sks-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sks-devel] Min. Requirement for SKS Version in the Pool


From: John Clizbe
Subject: Re: [Sks-devel] Min. Requirement for SKS Version in the Pool
Date: Mon, 25 Jun 2012 20:52:03 -0500
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.20pre) Gecko/20110606 Mnenhy/0.8.5 SeaMonkey/2.0.15pre

Jeffrey Johnson wrote:
> 
> On Jun 25, 2012, at 10:24 AM, Phil Benchoff wrote:
> 
>> On Sun, Jun 24, 2012 at 09:20:07PM +0200, Kristian Fiskerstrand wrote:
>>> As of *1. August 2012* I intend to change the minimum version for
>>> qualification in the pool to 1.1.3.
>> 
>> Our keyserver runs on Centos 5.7.  The distribution BDB is 4.3.29 and we
>> have ocaml 3.12.0.  The server is a VM.
>> 
>> * Is there a suggested version of BDB other than >= 4.6?  Any reason to 
>>  pick 4 versus 5?
> 
> Centos 5.7 ships many versions of Berkeley DB for "compatibility",
> not just db-4.3.29 uses in "system" db for clueless/busted versions
> of software that continues to build with
>       #include <db.h>
> 
> Instead, add db-5.3.x that installs into /usr/include/db53 and
> add -I/usr/include/db53 to build flags.
> 
> Shared llbraries will not collide, and linkage flags should be  -ldb-5.3,
> and pristine "vendor" software will not be disturbed whatsoever.

Both of these can be set in Makefile.include

BDBINCLUDE=/usr/include/db53
LIBDB=-ldb-5.3

> 
>> * Is there any need to build ocaml 3.12.1?
> 
> This I can't answer for sure, but I suspect you will need 3.12.1.

I know 3.11.0+ works. 3.12.0 should compile SKS fine.

>> * It looks like there is a patch for the VM clock issue.  Is it in 1.1.3?
> 
> VM time skew was a big deal around RHEL5 iirc, and it may be fixed
> in the kernel. I personally haven't seen time skew issues running in
> CentOS VM's in 2y without any patching.
> 
> But Phil Pennock's patch was posted in the last 4 weeks, quite easy,
> in archives.

It's included in the development trunk

-John



reply via email to

[Prev in Thread] Current Thread [Next in Thread]