Bug#630985: postinst: Isn't the paranoia in handling BerkeleyDB upgrades way too aggresive?

[Andreas Metzler]

On 2011-06-19 Regid Ichira <regid23 at yahoo.com> wrote:
> Package: exim4-base
> Version:  4.76-2
> Severity: normal

>   4.76-2's postinst has a paranoia code to handle BerkeleyDB upgrades.
> On any db upgrade, it throws away hints databases.
> 1. A possible ratelimit db is not mentioned.

Thanks for the hint, fixed in SVN.

> 2. I think the paranoia code is not required.  Won't an exim_dumpdb fail 
>     due to an incompatible upgrade? 
[...]

It should, however in the past berkeley-db sometimes has broken rather
spectacularily when given a incompatible file. See e.g. the resolution
to <http://bugs.debian.org/360696>. I think that the benefit of not
triggering stuff like this outweighs losing the hints once every two
years.

cu andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'