Valentin David authored Aug 08, 2018 and Qinusty committed Aug 21, 2018

Issue was introduced by 171e803f (include directive) and the fix was
found courtesy of @Qinusty. This fixes also the include
feature. Because elements are to be serialized, the included fragments
need to use copy_tree when loaded.

Related to #470.

Fix broken indentation after track

See merge request !622

Pipeline: Skip except_elements logic if no elements to except

See merge request !688

Chandan Singh authored Aug 21, 2018 and Tristan Van Berkom committed Aug 21, 2018

These new images come with pinned versions of `pytest` and `pylint`:

- `pylint`: `== 2.1.1`
- `pytest`: `>= 3.7`

Chandan Singh authored Aug 21, 2018 and Tristan Van Berkom committed Aug 21, 2018

These packages should only be updated as a deliberate change and the
code should be tested with the new versions to ensure that the test
still pass.

Any future updates should also happen in sync with the
buildstream-docker-images repository so that the testsuite base images
also enforce the same restrictions for the development requirements.

Replaces BuildStream/buildstream!684.

Restrict pylint/pytest versions and bump CI tags

See merge request !689

Qinusty authored Aug 21, 2018 and Qinusty committed Aug 21, 2018

Providing warn with detail=None (default) will no longer print None when
a fatal warning is triggered.

Fatal warnings no longer print None when detail=None

See merge request !694

Fill out those fields in `setup.py` that are required for publishing a
package on PyPi.

Part of #587.

setup.py: Add fields required for publishing on PyPi

See merge request !695

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

_frontend/linuxapp.py: Fix special casing around desktop notification escape sequence

Closes #385

See merge request !692

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 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.