On Friday 29 July 2005 10:48, Torsten Homeyer wrote:
> Steffen Hansen wrote:
> > I wonder why it says to upgrade everything but db and imapd before
> > running db_recover. Couldn't you just do that before starting to
> > upgrade at all?
>
> Because it eventually takes some time to upgrade all packa
Steffen Hansen wrote:
I wonder why it says to upgrade everything but db and imapd before
running db_recover. Couldn't you just do that before starting to
upgrade at all?
Because it eventually takes some time to upgrade all packages and if you
don't want to have the service down for an extend
On Thursday 28 July 2005 13:21, Torsten Homeyer wrote:
> Torsten Homeyer wrote:
> > This it not really necessary. This Problem is known from OpenPKG
> > 2.2 to 2.3 upgrade already and there is a description in the
> > OpenPKG Wiki on how to do the upgrade.
>
> You will find it under http://wiki.ope
Torsten Homeyer wrote:
This it not really necessary. This Problem is known from OpenPKG 2.2 to
2.3 upgrade already and there is a description in the OpenPKG Wiki on
how to do the upgrade.
You will find it under http://wiki.openpkg.org/?HintPackageImapd
tho
--
SpaceNet AG
Ralf S. Engelschall wrote:
On Wed, Jul 27, 2005, Steffen Hansen wrote:
After upgrading from openpkg-2.2 to 2.4 we have a problem with more or
less all bdb database because Berkeley DB was upgraded from 4.2 to 4.3.
This affects for example Cyrus imapd.
Are there any thoughts about either maint
On Wed, Jul 27, 2005, Steffen Hansen wrote:
> After upgrading from openpkg-2.2 to 2.4 we have a problem with more or
> less all bdb database because Berkeley DB was upgraded from 4.2 to 4.3.
> This affects for example Cyrus imapd.
>
> Are there any thoughts about either maintaining a db4.2 package
