From: Jim Rees <rees@umich.edu>
To: NeilBrown <neilb@suse.de>
Cc: Steve Dickson <SteveD@redhat.com>,
Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: ANNOUNCE: nfs-utils-1.2.5 released.
Date: Sun, 25 Sep 2011 10:13:01 -0400 [thread overview]
Message-ID: <20110925141301.GB5021@umich.edu> (raw)
In-Reply-To: <20110925183930.69b33573@notabene.brown>
NeilBrown wrote:
On Sat, 24 Sep 2011 08:55:57 -0400 Steve Dickson <SteveD@redhat.com> wrote:
> New Features in this release:
>
> * With the addition of the blkmapd daemon, the client
> now supports every pNFS layout type.
>
> * The usual assorted bug fixes.
>
> The tarball can only be found at Sourceforge.net since
> master.kernel.org is still down:
>
> http://sourceforge.net/projects/nfs
>
> [ Maybe we should start thinking about putting the rpms on linux-nfs.org?? ]
>
> The git tree is at:
> git://linux-nfs.org/nfs-utils
>
> The change log is also only on Sourceforge.net:
>
> http://sourceforge.net/projects/nfs/files/nfs-utils/1.2.5/Changelog-1.2.5/download
>
I've packaged this up for openSUSE so it should appear in openSUSE:Factory
and probably openSUSE:Tumbleweed in a day or two.
Only oddity I noticed is that the configure script doesn't check for
libdevmapper.h so I get a complaint when compiling instead of when
configuring. I don't know if that is a good thing or a bad thing, but I
thought I would mention it.
Sorry, I'm not good with automake. The dependency is from blkmapd on
libdevmapper so there should be a check on both the header and the library,
contingent on nfsv41. I'll see if I can cook up a patch. Thanks for
catching this.
next prev parent reply other threads:[~2011-09-25 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 12:55 ANNOUNCE: nfs-utils-1.2.5 released Steve Dickson
2011-09-25 5:10 ` Benny Halevy
2011-09-26 10:28 ` Steve Dickson
2011-09-25 8:39 ` NeilBrown
2011-09-25 14:13 ` Jim Rees [this message]
2011-09-26 10:40 ` Steve Dickson
2011-09-25 16:56 ` Jim Rees
2011-09-26 11:45 ` Steve Dickson
2011-09-26 12:16 ` Jim Rees
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=20110925141301.GB5021@umich.edu \
--to=rees@umich.edu \
--cc=SteveD@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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).