From 75808db17caf8b960b351e3408e74142f4c85aac Mon Sep 17 00:00:00 2001
From: Daniel Baumann <daniel.baumann@progress-linux.org>
Date: Sun, 14 Apr 2024 15:42:30 +0200
Subject: Adding upstream version 2.117.0.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
---
 tags/b/build-depends-on-python-dev-with-no-arch-any.tag | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
 create mode 100644 tags/b/build-depends-on-python-dev-with-no-arch-any.tag

(limited to 'tags/b/build-depends-on-python-dev-with-no-arch-any.tag')

diff --git a/tags/b/build-depends-on-python-dev-with-no-arch-any.tag b/tags/b/build-depends-on-python-dev-with-no-arch-any.tag
new file mode 100644
index 0000000..bfba2aa
--- /dev/null
+++ b/tags/b/build-depends-on-python-dev-with-no-arch-any.tag
@@ -0,0 +1,15 @@
+Tag: build-depends-on-python-dev-with-no-arch-any
+Severity: info
+Check: fields/package-relations
+Explanation: The given package appears to have a Python development package
+ (<code>python3-dev</code>, <code>python3-all-dev</code> or
+ <code>pythonX.Y-dev</code>) listed in its <code>Build-Depends</code> or
+ <code>Build-Depends-Indep</code> fields, but only <code>Architecture: all</code>
+ packages are built by this source package. Python applications and modules
+ do not usually require those dev packages, so you should consider removing
+ them in favour of <code>python3</code>, <code>python3-all</code>
+ or <code>pythonX.Y</code>.
+ .
+ If you are building a Python extension instead, you should have
+ development packages listed in <code>Build-Depends</code>, but normally there should
+ be at least one <code>Architecture: any</code> package.
-- 
cgit v1.2.3