public inbox for hail-devel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Samba - BoYang <boyang@samba.org>, hail-devel@vger.kernel.org
Subject: Re: CLD doesn't build on db-4.3
Date: Thu, 1 Apr 2010 14:50:10 -0600	[thread overview]
Message-ID: <20100401145010.0204151a@redhat.com> (raw)
In-Reply-To: <4BB4B5D4.2000300@garzik.org>

On Thu, 01 Apr 2010 11:03:48 -0400
Jeff Garzik <jeff@garzik.org> wrote:

> >      It won't build on db-4.4, either. probably won't build on db-4.5, as
> > db-5.0 says DBC->xxx was introduced in db-4.6. :-) Should we disable
> > support for 4.3 - 4.5 and add 4.9 - 5.0?
> 
> I'd answer "yes", by a circuitous route:  if I understand things 
> correctly, the replicated PAXOS db4 backend that we are heading towards 
> (see the 'replica' branch of 
> git://git.kernel.org/pub/scm/daemon/cld/cld.git) was buggy in early db4 
> releases.

> Therefore, it sounds like we could eliminate two issues with a single 
> change, by removing support for db 4.3 - 4.5, the DBC issue and the 
> PAXOS issue.

RHEL 5 ships with db4-4.3.29-10.el5 (I checked for Bo's problem
this morning), so dropping 4.3 will make RHEL 5 unsupportable.
Just a point to consider.

-- Pete

  reply	other threads:[~2010-04-01 20:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 11:01 CLD doesn't build on db-4.3 Samba - BoYang
2010-04-01 13:56 ` Pete Zaitcev
2010-04-01 15:03 ` Jeff Garzik
2010-04-01 20:50   ` Pete Zaitcev [this message]
2010-04-02  0:38     ` Samba - BoYang
2010-04-02  0:35   ` Samba - BoYang
2010-04-14  4:32     ` Jeff Garzik
2010-04-14  4:59       ` Pete Zaitcev
2010-04-14 10:44       ` Here is small patch to enable link against higher-version db for nfs4d and tabled. :-) Samba - BoYang
2010-04-14 13:40         ` Jeff Garzik
2010-04-14 13:50           ` Samba - BoYang

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=20100401145010.0204151a@redhat.com \
    --to=zaitcev@redhat.com \
    --cc=boyang@samba.org \
    --cc=hail-devel@vger.kernel.org \
    --cc=jeff@garzik.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