On Mon, Apr 18, 2011 at 12:50, Jeroen van Meeuwen (Kolab Systems)
wrote:
> Bron Gondwana wrote:
>
>> I really, really wanted to have BDB able to handle in-place upgrades
>
>> as well, but I haven't been able to figure out a way. There is an
>
>> ->upgrade method on databases, but it says it's dest
Bron Gondwana wrote:
> I really, really wanted to have BDB able to handle in-place upgrades
> as well, but I haven't been able to figure out a way. There is an
> ->upgrade method on databases, but it says it's destructive and can
> fail
If I understood it correctly, I think it actually says that
On Sun, Apr 17, 2011 at 19:55, Bron Gondwana wrote:
> On Tue, Apr 05, 2011 at 02:58:12AM +0200, Ondřej Surý wrote:
>> You cannot backup (using DB_ENV->archive) before you upgrade, but if
>> you find a way how to call (backend)->init with CYRUSDB_UPGRADE flag
>> and them (backend)->open with same f
On Tue, Apr 05, 2011 at 02:58:12AM +0200, Ondřej Surý wrote:
> You cannot backup (using DB_ENV->archive) before you upgrade, but if
> you find a way how to call (backend)->init with CYRUSDB_UPGRADE flag
> and them (backend)->open with same flag, the attached patch should do
> the trick. (But I advi
On Sun, Apr 17, 2011 at 07:37:35PM +0200, Ondřej Surý wrote:
> On Tue, Apr 5, 2011 at 02:58, Ondřej Surý wrote:
> > You cannot backup (using DB_ENV->archive) before you upgrade, but if
> > you find a way how to call (backend)->init with CYRUSDB_UPGRADE flag
> > and them (backend)->open with same f
On Tue, Apr 5, 2011 at 02:58, Ondřej Surý wrote:
> On Tue, Apr 5, 2011 at 01:08, Bron Gondwana wrote:
>> On Tue, Apr 05, 2011 at 12:28:02AM +0200, Ondřej Surý wrote:
>>> > I really, really wanted to have BDB able to handle in-place upgrades
>>> > as well, but I haven't been able to figure out a w
On Tue, Apr 5, 2011 at 01:08, Bron Gondwana wrote:
> On Tue, Apr 05, 2011 at 12:28:02AM +0200, Ondřej Surý wrote:
>> > I really, really wanted to have BDB able to handle in-place upgrades
>> > as well, but I haven't been able to figure out a way. There is an
>> > ->upgrade method on databases, bu
On Tue, Apr 05, 2011 at 12:28:02AM +0200, Ondřej Surý wrote:
> > I really, really wanted to have BDB able to handle in-place upgrades
> > as well, but I haven't been able to figure out a way. There is an
> > ->upgrade method on databases, but it says it's destructive and can
> > fail - so you can'
> I really, really wanted to have BDB able to handle in-place upgrades
> as well, but I haven't been able to figure out a way. There is an
> ->upgrade method on databases, but it says it's destructive and can
> fail - so you can't just run it during the startup process and hope...
> unless you tak
On Fri, Apr 01, 2011 at 10:09:26PM +0200, Ondřej Surý wrote:
> On Fri, Apr 1, 2011 at 20:58, Bron Gondwana wrote:
> > On Fri, Apr 01, 2011 at 07:09:11PM +0200, Ondřej Surý wrote:
> >> I'll try to dig into that. I took (how foolish) the maintainership of bdb
> >> in debian, which was orphaned by p
On Fri, Apr 1, 2011 at 20:58, Bron Gondwana wrote:
> On Fri, Apr 01, 2011 at 07:09:11PM +0200, Ondřej Surý wrote:
>> I'll try to dig into that. I took (how foolish) the maintainership of bdb in
>> debian, which was orphaned by previous maintainer. So I'll have to get
>> accustomed with bdb anywa
On Fri, Apr 01, 2011 at 07:09:11PM +0200, Ondřej Surý wrote:
> I'll try to dig into that. I took (how foolish) the maintainership of bdb in
> debian, which was orphaned by previous maintainer. So I'll have to get
> accustomed with bdb anyway.
Do you have an account on Cyrus bugzilla? Then I can
I'll try to dig into that. I took (how foolish) the maintainership of bdb in
debian, which was orphaned by previous maintainer. So I'll have to get
accustomed with bdb anyway.
Ondřej Surý
On 1.4.2011, at 18:24, Bron Gondwana wrote:
> On Fri, 1 Apr 2011 16:48:55 +0200
> Ondřej Surý wrote:
>
On Fri, 1 Apr 2011 16:48:55 +0200
Ondřej Surý wrote:
> Hi,
>
> with recent (kinda accidental) upload of 2.4 to debian unstable the
> need for automatic conversion from older database format (2.2) to the
> new one (2.4) yet again arised. Anyone already has something written
> or is willing to hel
Hi,
with recent (kinda accidental) upload of 2.4 to debian unstable the
need for automatic conversion from older database format (2.2) to the
new one (2.4) yet again arised. Anyone already has something written
or is willing to help write one?
O.
--
Ondřej Surý
15 matches
Mail list logo
