From: Bastian Germann <bastiangermann@fishpost.de>
To: linux-xfs@vger.kernel.org
Cc: Bastian Germann <bastiangermann@fishpost.de>,
Helmut Grohne <helmut@subdivi.de>
Subject: [PATCH 1/3] debian: Drop unused dh-python from Build-Depends
Date: Fri, 5 Feb 2021 01:31:23 +0100 [thread overview]
Message-ID: <20210205003125.24463-2-bastiangermann@fishpost.de> (raw)
In-Reply-To: <20210205003125.24463-1-bastiangermann@fishpost.de>
xfsprogs participates in dependency loops relevant to architecture
bootstrap. Identifying easily droppable dependencies, it was found
that xfsprogs does not use dh-python in any way.
Reported-by: Helmut Grohne <helmut@subdivi.de>
Signed-off-by: Bastian Germann <bastiangermann@fishpost.de>
---
debian/changelog | 6 ++++++
debian/control | 2 +-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/debian/changelog b/debian/changelog
index ce4a224d..7b0120c2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+xfsprogs (5.10.0-3) unstable; urgency=medium
+
+ * Drop unused dh-python from Build-Depends (Closes: #981361)
+
+ -- Bastian Germann <bastiangermann@fishpost.de> Fri, 05 Feb 2021 00:18:31 +0100
+
xfsprogs (5.10.0-2) unstable; urgency=low
* Team upload
diff --git a/debian/control b/debian/control
index b0eb1566..8975bd13 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: admin
Priority: optional
Maintainer: XFS Development Team <linux-xfs@vger.kernel.org>
Uploaders: Nathan Scott <nathans@debian.org>, Anibal Monsalve Salazar <anibal@debian.org>, Bastian Germann <bastiangermann@fishpost.de>
-Build-Depends: libinih-dev, uuid-dev, dh-autoreconf, debhelper (>= 5), gettext, libtool, libedit-dev, libblkid-dev (>= 2.17), linux-libc-dev, libdevmapper-dev, libattr1-dev, libicu-dev, dh-python, pkg-config
+Build-Depends: libinih-dev, uuid-dev, dh-autoreconf, debhelper (>= 5), gettext, libtool, libedit-dev, libblkid-dev (>= 2.17), linux-libc-dev, libdevmapper-dev, libattr1-dev, libicu-dev, pkg-config
Standards-Version: 4.0.0
Homepage: https://xfs.wiki.kernel.org/
--
2.30.0
next prev parent reply other threads:[~2021-02-05 0:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 0:31 [PATCH 0/3] debian: minor fixes Bastian Germann
2021-02-05 0:31 ` Bastian Germann [this message]
2021-02-05 0:51 ` [PATCH 1/3] debian: Drop unused dh-python from Build-Depends Darrick J. Wong
2021-02-05 4:49 ` Eric Sandeen
2021-02-05 18:05 ` Bastian Germann
2021-02-05 18:18 ` Darrick J. Wong
2021-02-05 0:31 ` [PATCH 2/3] debian: Only build for Linux Bastian Germann
2021-02-05 0:48 ` Darrick J. Wong
2021-02-05 0:31 ` [PATCH 3/3] debian: Prevent installing duplicate changelog Bastian Germann
2021-02-05 0:49 ` Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210205003125.24463-2-bastiangermann@fishpost.de \
--to=bastiangermann@fishpost.de \
--cc=helmut@subdivi.de \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox