summaryrefslogtreecommitdiffstats
path: root/tags/s/source-contains-bzr-control-dir.tag
diff options
context:
space:
mode:
Diffstat (limited to 'tags/s/source-contains-bzr-control-dir.tag')
-rw-r--r--tags/s/source-contains-bzr-control-dir.tag9
1 files changed, 9 insertions, 0 deletions
diff --git a/tags/s/source-contains-bzr-control-dir.tag b/tags/s/source-contains-bzr-control-dir.tag
new file mode 100644
index 0000000..6d5a72e
--- /dev/null
+++ b/tags/s/source-contains-bzr-control-dir.tag
@@ -0,0 +1,9 @@
+Tag: source-contains-bzr-control-dir
+Severity: pedantic
+Check: files/artifact
+Explanation: The upstream source contains a .bzr directory. It was most likely
+ included by accident since bazaar-ng version control directories usually
+ don't belong in releases and may contain the entire repository. When
+ packaging a bzr snapshot, use bzr export to create a clean tree. If an
+ upstream release tarball contains .bzr directories, you should usually
+ report this as a bug upstream.