From: Andreas Dilger <adilger-xsfywfwIY+M@public.gmane.org>
To: Scott James Remnant <scott-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
Cc: linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Theodore Tso <tytso-3s7WtUTddSA@public.gmane.org>,
util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] debian: Remove blkid packages
Date: Fri, 17 Jul 2009 02:43:28 -0400 [thread overview]
Message-ID: <20090717064328.GI4207@webber.adilger.int> (raw)
In-Reply-To: <E1MRWBp-0000yr-Sq-eEhpo0tUqaMrEHDPZeG1zdBPR1lH4CV8@public.gmane.org>
On Jul 16, 2009 19:56 +0100, Scott James Remnant wrote:
> -Build-Depends: texi2html (>= 1.76), gettext, texinfo, dc, pkg-config, dietlibc-dev (>> 0.30) [alpha amd64 arm hppa i386 ia64 mips mipsel powerpc ppc64 s390 sparc], debhelper (>= 7.0)
> +Build-Depends: texi2html (>= 1.76), gettext, texinfo, dc, pkg-config, dietlibc-dev (>> 0.30) [alpha amd64 arm hppa i386 ia64 mips mipsel powerpc ppc64 s390 sparc], debhelper (>= 7.0), libblkid-dev (>= 2.16)
Should this really _require_ the util-linux (2.16) version of libblkid-dev?
Wouldn't an older e2fsprogs-based package be sufficient?
> -Package: libblkid-dev
Since the old package also provided "libblkid-dev" it doesn't necessarily
mean that package is obsolete. If someone needs to install a new version
of e2fsprogs to fix a filesystem problem on an old system, they shouldn't
necessarily also have to install a new version of util-linux, which might
have all sorts of other dependencies, etc...
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-07-17 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 18:56 [PATCH] debian: Remove blkid packages Scott James Remnant
[not found] ` <E1MRWBp-0000yr-Sq-eEhpo0tUqaMrEHDPZeG1zdBPR1lH4CV8@public.gmane.org>
2009-07-17 6:43 ` Andreas Dilger [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=20090717064328.GI4207@webber.adilger.int \
--to=adilger-xsfywfwiy+m@public.gmane.org \
--cc=linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=scott-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org \
--cc=tytso-3s7WtUTddSA@public.gmane.org \
--cc=util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).