From: Christoph Hellwig <hch@infradead.org>
To: Nathan Scott <nscott@aconex.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfsprogs spec file update
Date: Sun, 25 Jan 2009 00:00:46 -0500 [thread overview]
Message-ID: <20090125050046.GB3979@infradead.org> (raw)
In-Reply-To: <1232777667.13684.20.camel@verge.scott.net.au>
On Sat, Jan 24, 2009 at 05:14:27PM +1100, Nathan Scott wrote:
> 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).
Looks good to me, even without any real uptodate rpm knowledge..
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-25 5:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 6:14 [PATCH] xfsprogs spec file update Nathan Scott
2009-01-25 5:00 ` Christoph Hellwig [this message]
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=20090125050046.GB3979@infradead.org \
--to=hch@infradead.org \
--cc=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