delta/buildstream.git, branch valentindavid/inconsistant-workspace gitlab.com: buildstream/buildstream.git Improve error message for deleted open workspaces 2018-08-22T18:31:43+00:00 Valentin David valentin.david@codethink.co.uk 2018-08-22T18:31:43+00:00 1479b32c75e8d1153be148ce3b06b26e743f8da8 Fixes #576. 
Fixes #576.
Merge branch 'tristan/debug-symbols-location' into 'master' 2018-08-22T11:39:32+00:00 Tristan Van Berkom tristan.van.berkom@gmail.com 2018-08-22T11:39:32+00:00 5b79bbb725bfa52689bcd8bfeddd15ce4d1ecd5d Don't strip pathname from debug symbol files See merge request BuildStream/buildstream!697 
Don't strip pathname from debug symbol files

See merge request BuildStream/buildstream!697
 Don't strip pathname from debug symbol files 2018-08-22T10:38:41+00:00 Sam Thursfield sam@afuera.me.uk 2018-07-03T17:20:56+00:00 f4e51cf1042307cdd45ee34c761424e7848ccc26 When GDB looks for debug symbols it looks for the full path of the file inside the configured debug-file-directory. For example, if the debug-file-directory is set to a default of /usr/lib/debug, and you are debugging /usr/bin/python3, GDB will look for its debug symbols at this location: /usr/lib/debug/usr/bin/python3. BuildStream has been putting all debug files inside /usr/lib/debug under their $(basename), so in the above example GDB would fail to find any debug symbols for /usr/bin/python3 because they would be in the incorrect locatoin of /usr/lib/debug/python3. 
When GDB looks for debug symbols it looks for the full path of the file
inside the configured debug-file-directory. For example, if the
debug-file-directory is set to a default of /usr/lib/debug, and you are
debugging /usr/bin/python3, GDB will look for its debug symbols at this
location: /usr/lib/debug/usr/bin/python3.

BuildStream has been putting all debug files inside /usr/lib/debug
under their $(basename), so in the above example GDB would fail to find
any debug symbols for /usr/bin/python3 because they would be in the
incorrect locatoin of /usr/lib/debug/python3.
Merge branch 'willsalmon/versionTagRegrex' into 'master' 2018-08-22T09:33:04+00:00 Will Salmon will.salmon@codethink.co.uk 2018-08-22T09:33:04+00:00 ff52ae18cf779f109081c33937b8f123780b69b5 Search for tags with the *.*.* patten for version See merge request BuildStream/buildstream!601 
Search for tags with the *.*.* patten for version

See merge request BuildStream/buildstream!601
 Search for tags with the *.*.* patten for version 2018-08-22T08:05:28+00:00 William Salmon will.salmon@codethink.co.uk 2018-08-03T14:16:05+00:00 e15f5fa339242f6402836b0fb73074ff370401ba This has been done in a way that I hope might be able to be upstreamed in to versioneer. This is not garanteed but it would be good if it could be. Please see https://github.com/warner/python-versioneer/pull/186 and https://github.com/wsalmonct/python-versioneer/tree/feature/regexTags for further details. 
This has been done in a way that I hope might be able to be upstreamed
in to versioneer. This is not garanteed but it would be good if it
could be.

Please see https://github.com/warner/python-versioneer/pull/186 and
https://github.com/wsalmonct/python-versioneer/tree/feature/regexTags
for further details.
Catch Non Numeric versions 2018-08-22T08:05:28+00:00 William Salmon will.salmon@codethink.co.uk 2018-08-03T14:53:53+00:00 eeaddbac923c49b8a9cde5aa411233d850dabbc4 This patch just displays a better message than the default stack trace but dose not try to fix the problem. A further patch will be created but it effects versioneer so may take longer to land as it may need to go via versioneer mainline. 
This patch just displays a better message than the default stack trace
but dose not try to fix the problem. A further patch will be created but
it effects versioneer so may take longer to land as it may need to go
via versioneer mainline.
Merge branch 'tristan/notifications' into 'master' 2018-08-22T06:24:12+00:00 Tristan Van Berkom tristan.van.berkom@gmail.com 2018-08-22T06:24:12+00:00 c8bafb687e1ac2c2692f69c0e6f0bb80a2cb7565 _frontend/linuxapp.py: Fix special casing around desktop notification escape sequence Closes #385 See merge request BuildStream/buildstream!692 
_frontend/linuxapp.py: Fix special casing around desktop notification escape sequence

Closes #385

See merge request BuildStream/buildstream!692
 _frontend/linuxapp.py: Fix special casing around desktop notification escape sequence 2018-08-22T05:24:42+00:00 Tristan Van Berkom tristan.vanberkom@codethink.co.uk 2018-08-20T09:13:43+00:00 3d4e649df8acffe3abbd27f393ef1cc981ea2580 Now we allow the notification to happen on any TERM which starts with 'xterm' or 'vte', and we only do it if the VTE_VERSION is >= 4600, where we know for sure that VTE will not print garbage on the terminal. Fixes #385 
Now we allow the notification to happen on any TERM
which starts with 'xterm' or 'vte', and we only do it
if the VTE_VERSION is >= 4600, where we know for sure that
VTE will not print garbage on the terminal.

Fixes #385
Merge branch 'chandan/pypi-prep' into 'master' 2018-08-22T05:23:33+00:00 Tristan Van Berkom tristan.van.berkom@gmail.com 2018-08-22T05:23:33+00:00 81278f84dffd7e499c5fb5be1e1685300ac28387 setup.py: Add fields required for publishing on PyPi See merge request BuildStream/buildstream!695 
setup.py: Add fields required for publishing on PyPi

See merge request BuildStream/buildstream!695
 setup.py: Add fields required for publishing on PyPi 2018-08-21T23:47:32+00:00 Chandan Singh csingh43@bloomberg.net 2018-06-30T02:31:17+00:00 ab1caac195d1f136c4bb0150cc500ba6d3504a75 Fill out those fields in `setup.py` that are required for publishing a package on PyPi. Part of https://gitlab.com/BuildStream/buildstream/issues/587. 
Fill out those fields in `setup.py` that are required for publishing a
package on PyPi.

Part of https://gitlab.com/BuildStream/buildstream/issues/587.