I'd add my vote to bundling Berkeley DB with SKS. In fact, I've said the
same of applications that utilize sqlite for similar reasons.
Best Wishes,
ClarusComms OpenPGP Services
open...@claruscomms.net
On 8/19/13 17:40 , Jeffrey Johnson wrote:
>
> On Aug 19, 2013, at 6:30 PM, Daniel Kahn Gillmo
On Aug 19, 2013, at 6:30 PM, Daniel Kahn Gillmor wrote:
> On 08/16/2013 10:03 AM, James Cloos wrote:
>> It looks like this might be a debian error.
>>
>> sks-1.1.4 from debian experimental fails reliably when using sid, as of
>> the latest upgrade to libdb5.1 (5.1.29-7) in sid.
>
> thanks for r
On 08/16/2013 10:03 AM, James Cloos wrote:
> It looks like this might be a debian error.
>
> sks-1.1.4 from debian experimental fails reliably when using sid, as of
> the latest upgrade to libdb5.1 (5.1.29-7) in sid.
thanks for reporting this as http://bugs.debian.org/719876 -- it sounds
to me li
Hello.
On 08/16/2013 06:03 PM, James Cloos wrote:
> It looks like this might be a debian error.
>
> sks-1.1.4 from debian experimental fails reliably when using sid, as of
> the latest upgrade to libdb5.1 (5.1.29-7) in sid.
>
> Jessie, as of today, still has the previous version (5.1.29-6) accor
It looks like this might be a debian error.
sks-1.1.4 from debian experimental fails reliably when using sid, as of
the latest upgrade to libdb5.1 (5.1.29-7) in sid.
Jessie, as of today, still has the previous version (5.1.29-6) according
to http://packages.debian.org/search?keywords=db5.1.
1.1.
I mistyped restart for reload today, and now sks will not start.
db_verify shows an extensive quantity of errors in both PTree/ptree,
DB/key and a few in DB/keyid. Most are of the form:
db_verify: Page 1031: invalid next_pgno 1006960
db_verify: Page 1032: invalid prev_pgno 1006960
db_recove
