From: Nathan Scott <nscott@aconex.com>
To: xfs@oss.sgi.com
Subject: [PATCH] xfsprogs spec file update
Date: Sat, 24 Jan 2009 17:14:27 +1100 [thread overview]
Message-ID: <1232777667.13684.20.camel@verge.scott.net.au> (raw)
Since binaries have moved between xfsprogs and xfsdump packages
in version 3.0.0, we need to fix the dependencies in the rpm
specfiles, else rpm will complain.
While in there, remove xfs-cmds Provides/Obsoletes lines, there
is no way anyone is ever going to be requiring those anymore (no
real-world upgrade path having such old skool SGI-released rpms).
diff --git a/build/rpm/xfsprogs.spec.in b/build/rpm/xfsprogs.spec.in
index 2826a37..cf61225 100644
--- a/build/rpm/xfsprogs.spec.in
+++ b/build/rpm/xfsprogs.spec.in
@@ -5,10 +5,8 @@ Release: @pkg_release@
Distribution: @pkg_distribution@
Packager: Silicon Graphics, Inc. <http://www.sgi.com/>
BuildRoot: @build_root@
-Provides: xfs-cmds
-Obsoletes: xfs-cmds
Prereq: /sbin/ldconfig
-Conflicts: xfsdump < 2.0.0
+Conflicts: xfsdump < 3.0.0
Source: @pkg_name@-@pkg_version@.src.tar.gz
License: GPL
Vendor: Silicon Graphics, Inc.
@@ -32,8 +30,8 @@ with the IRIX version of XFS.
%package devel
Summary: XFS filesystem-specific static libraries and headers.
Group: Development/Libraries
-Requires: @pkg_name@ >= 2.0.0
-Conflicts: @pkg_name@ < 2.0.0
+Requires: @pkg_name@ >= 3.0.0
+Conflicts: @pkg_name@ < 3.0.0
%description devel
xfsprogs-devel contains the libraries and header files needed to
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-01-24 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 6:14 Nathan Scott [this message]
2009-01-25 5:00 ` [PATCH] xfsprogs spec file update Christoph Hellwig
2009-01-25 14:21 ` Eric Sandeen
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=1232777667.13684.20.camel@verge.scott.net.au \
--to=nscott@aconex.com \
--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