Your message dated Wed, 21 Aug 2013 17:47:48 -0400
with message-id <[email protected]>
and subject line Re: Bug#719876: unable to replicate sks 1.1.4 failure against
libdb5.1 5.1.29-7
has caused the Debian Bug report #719876,
regarding sks: db update broke sks
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
719876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719876
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sks
Version: 1.1.4 (experimental)
Severity: important
The recent upgrade to db (5.1.29-7) broke sks databases built against
the previous minor release (5.1.29-6, I presume).
A restart w/o re-doing the database from scratch fails, complaining
about errors in the database.
The db utils do not fix it, as far as I was able to test.
I kept a copy of the b0rked database, in case anyone wants to look at
it, but it is huge.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
It looks like the bug was a hardware issue with the box hosting my vm.
The evidence to that effect only became clear after I posted this report,
especially after I (also) was unable to replicate it on another box
I wanted to give it a couple of days to be sure, since it took about
that long for the corruption to occur on the original vm. It seems to
be working properly.
Appologies for the false alarm. sks was the only thing on the vm which
triggered the filesystem corruption; nothing else I ran there did much
other than append to or replace files. That made it look at first like
an application layer problem.
-JimC
--
James Cloos <[email protected]> OpenPGP: 1024D/ED7DAEA6
--- End Message ---
