On Fri, May 29, 2009 at 09:38:59PM +0200, Florian Weimer wrote:
* Jonathan McDowell:
I'd like to upload a new onak package to stable to fix #520117 by
rebuilding against db4.5 instead of db4.6 - I'm hitting what seems to be
#510270 in db4.6.
Shouldn't this be fixed in db4.6 instead?
That would be nicest, but I haven't seen any movement on it. db4.5 and
db4.7 both don't seem to have the issue and it only happens when opening
read-only afaict. I don't have the time to delve into the depths of
db4.6 and I've had several complaints about onak being broken as a
result of this.
On Fri, May 29, 2009 at 10:20:21PM +0200, Julien Cristau wrote:
On Fri, May 29, 2009 at 14:11:31 +0100, Jonathan McDowell wrote:
I'd like to upload a new onak package to stable to fix #520117 by
rebuilding against db4.5 instead of db4.6 - I'm hitting what seems to be
#510270 in db4.6.
Can db4.5 read files written by 4.6 without problems?
Bugger. I was sure I'd tried this, but either I hadn't or I got lucky. I
can reliably make things break by going 4.6 -> 4.5 with no other
changes. Which means I have to go for the more invasive approach of
disabling opening the DB read-only, which makes 4.6 work (instead of
failing after a dozen or so repeated attempts it can happily go for at
least 24,000). Revised diff attached.