From: Nathan Scott <nathans@debian.org>
To: xfs@oss.sgi.com
Subject: [patch] xfsprogs: add debian linux-libc-dev build dependency
Date: Wed, 1 Feb 2012 10:07:08 +1100 (EST) [thread overview]
Message-ID: <419906537.69741.1328051228836.JavaMail.root@acxmail-au2.aconex.com> (raw)
In-Reply-To: <1317955640.69734.1328051152460.JavaMail.root@acxmail-au2.aconex.com>
[-- Attachment #1: Type: text/plain, Size: 256 bytes --]
Add a build dependency on linux-libc-dev, to ensure we build
packages with have_fiemap set to true if the headers support
it. Noticed by Dave, some package builds didn't enable this
when they should have.
Signed-off-by: Nathan Scott <nathans@debian.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: debiandeps.patch --]
[-- Type: text/x-patch; name=debiandeps.patch, Size: 673 bytes --]
diff --git a/debian/control b/debian/control
index ca517ad..502b48b 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: admin
Priority: optional
Maintainer: XFS Development Team <xfs@oss.sgi.com>
Uploaders: Nathan Scott <nathans@debian.org>, Anibal Monsalve Salazar <anibal@debian.org>
-Build-Depends: uuid-dev, autoconf, debhelper (>= 5), gettext, libtool, libreadline-gplv2-dev | libreadline5-dev, libblkid-dev (>= 2.17)
+Build-Depends: uuid-dev, autoconf, debhelper (>= 5), gettext, libtool, libreadline-gplv2-dev | libreadline5-dev, libblkid-dev (>= 2.17), linux-libc-dev
Standards-Version: 3.9.1
Homepage: http://oss.sgi.com/projects/xfs/
[-- Attachment #3: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next parent reply other threads:[~2012-01-31 23:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1317955640.69734.1328051152460.JavaMail.root@acxmail-au2.aconex.com>
2012-01-31 23:07 ` Nathan Scott [this message]
2012-02-02 11:35 ` [patch] xfsprogs: add debian linux-libc-dev build dependency Christoph Hellwig
2012-02-02 22:51 ` Dave Chinner
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=419906537.69741.1328051228836.JavaMail.root@acxmail-au2.aconex.com \
--to=nathans@debian.org \
--cc=xfs@oss.sgi.com \
/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