)]}'
{"openstack/python-barbicanclient/python-barbicanclient.spec.j2":[{"author":{"_account_id":22595,"name":"Stefan Nica","email":"snica@suse.com","username":"stefan.nica"},"change_message_id":"18b4b315444ca12bf9c066209e1c1f7c213f29da","unresolved":false,"context_lines":[{"line_number":39,"context_line":"Python library for accessing the API (the barbicanclient module), and a"},{"line_number":40,"context_line":"command-line script (barbican)."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"%package -n python3-barbicanclient"},{"line_number":43,"context_line":"Summary:        Client for the Barbican Key Management API"},{"line_number":44,"context_line":"Requires:       {{ py3(\u0027cliff\u0027) }}"},{"line_number":45,"context_line":"Requires:       {{ py3(\u0027keystoneauth1\u0027) }}"}],"source_content_type":"text/x-jinja2","patch_set":5,"id":"3fa7e38b_5bd64055","line":42,"updated":"2019-12-12 18:55:34.000000000","message":"This is not immediately obvious and I admit I\u0027m not up to date with the overall python3 migration strategy for rpm-packaging, but why do we still need to keep the spec for the python-barbicanclient package around if it doesn\u0027t actually package anything and it doesn\u0027t require python3-barbicanclient ?","commit_id":"2ee1888e285b468e0bb723185393a87180ad2085"},{"author":{"_account_id":7102,"name":"Thomas Bechtold","email":"thomas.bechtold@canonical.com","username":"toabctl"},"change_message_id":"aeee83a06304f835a3e5d67e22561df33a7dc78a","unresolved":false,"context_lines":[{"line_number":39,"context_line":"Python library for accessing the API (the barbicanclient module), and a"},{"line_number":40,"context_line":"command-line script (barbican)."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"%package -n python3-barbicanclient"},{"line_number":43,"context_line":"Summary:        Client for the Barbican Key Management API"},{"line_number":44,"context_line":"Requires:       {{ py3(\u0027cliff\u0027) }}"},{"line_number":45,"context_line":"Requires:       {{ py3(\u0027keystoneauth1\u0027) }}"}],"source_content_type":"text/x-jinja2","patch_set":5,"id":"3fa7e38b_9b4b515d","line":42,"in_reply_to":"3fa7e38b_5bd64055","updated":"2019-12-13 04:15:26.000000000","message":"I can\u0027t follow. Do you mean the python-barbicanclient.spec.j2 file?","commit_id":"2ee1888e285b468e0bb723185393a87180ad2085"},{"author":{"_account_id":22595,"name":"Stefan Nica","email":"snica@suse.com","username":"stefan.nica"},"change_message_id":"a3316538eb5f25b4bc4cd3dbb1f401f684d0f0a8","unresolved":false,"context_lines":[{"line_number":39,"context_line":"Python library for accessing the API (the barbicanclient module), and a"},{"line_number":40,"context_line":"command-line script (barbican)."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"%package -n python3-barbicanclient"},{"line_number":43,"context_line":"Summary:        Client for the Barbican Key Management API"},{"line_number":44,"context_line":"Requires:       {{ py3(\u0027cliff\u0027) }}"},{"line_number":45,"context_line":"Requires:       {{ py3(\u0027keystoneauth1\u0027) }}"}],"source_content_type":"text/x-jinja2","patch_set":5,"id":"3fa7e38b_861218b3","line":42,"in_reply_to":"3fa7e38b_9b4b515d","updated":"2019-12-13 08:21:02.000000000","message":"Yes, that\u0027s right. The spec defines both python-barbicanclient and the python3-barbicanclient sub-package. I argue that we can have both \"merged\" into python3-barbicanclient as the main package, but I\u0027m probably missing something.","commit_id":"2ee1888e285b468e0bb723185393a87180ad2085"}]}