public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastian Germann <bastiangermann@fishpost.de>
To: linux-xfs@vger.kernel.org
Cc: Bastian Germann <bastiangermann@fishpost.de>
Subject: [PATCH 4/4] debian: Build-depend on libinih-dev with udeb package
Date: Sat, 20 Feb 2021 13:16:09 +0100	[thread overview]
Message-ID: <20210220121610.3982-5-bastiangermann@fishpost.de> (raw)
In-Reply-To: <20210220121610.3982-1-bastiangermann@fishpost.de>

The first libinih Debian package version with udeb binary package is 53-1.
Debian bug #981662 documents the need for it:
xfsprogs-udeb depends on libinih1, not libinih1-udeb

Link: https://bugs.debian.org/981662
Signed-off-by: Bastian Germann <bastiangermann@fishpost.de>
---
 debian/changelog | 3 +++
 debian/control   | 2 +-
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index 6cc9926b..1879485d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -7,6 +7,9 @@ xfsprogs (5.11.0-rc0-1) experimental; urgency=medium
   [ Steve Langasek ]
   * Regenerate config.guess using debhelper
 
+  [ Bastian Germann ]
+  * Build-depend on libinih-dev with udeb package
+
  -- Bastian Germann <bastiangermann@fishpost.de>  Sat, 20 Feb 2021 11:57:31 +0100
 
 xfsprogs (5.10.0-3) unstable; urgency=medium
diff --git a/debian/control b/debian/control
index 1da8093d..e4ec897c 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, pkg-config
+Build-Depends: libinih-dev (>= 53), 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.1


      parent reply	other threads:[~2021-02-20 12:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20 12:16 [PATCH 0/4] debian: Integrate Debian/Ubuntu changes Bastian Germann
2021-02-20 12:16 ` [PATCH 1/4] debian: Drop trying to create upstream distribution Bastian Germann
2021-02-21  4:01   ` Dave Chinner
2021-02-23  3:07     ` Darrick J. Wong
2021-02-20 12:16 ` [PATCH 2/4] debian: Enable CET on amd64 Bastian Germann
2021-02-21  3:59   ` Dave Chinner
2021-02-21  4:02     ` NACK " Dimitri John Ledkov
2021-02-21  4:28       ` Dave Chinner
2021-02-21  4:32         ` Dimitri John Ledkov
2021-02-21 21:37           ` Dave Chinner
2021-02-20 12:16 ` [PATCH 3/4] debian: Regenerate config.guess using debhelper Bastian Germann
2021-02-21  4:11   ` Dave Chinner
2021-02-21  7:16     ` Steve Langasek
2021-02-21 22:04       ` Dave Chinner
2021-02-22  0:16         ` Steve Langasek
2021-02-22  2:44           ` Dave Chinner
2021-02-22 19:23             ` Eric Sandeen
2021-02-23 20:51               ` Dave Chinner
2021-02-20 12:16 ` Bastian Germann [this message]

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=20210220121610.3982-5-bastiangermann@fishpost.de \
    --to=bastiangermann@fishpost.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