[horde] Attempting Upgrade For Horde 4

[Michael J Rubinsky]

Quoting Brian Spraker <spraker at yahoo.com>:

> --- On Tue, 7/31/12, Michael J Rubinsky <mrubinsk at horde.org> wrote:
>
>> From: Michael J Rubinsky <mrubinsk at horde.org>
>> Subject: Re: [horde] Attempting Upgrade For Horde 4
>> To: horde at lists.horde.org
>> Date: Tuesday, July 31, 2012, 8:50 AM
>>
>> Quoting Brian Spraker <spraker at yahoo.com>:
>>
>> > Hello all,
>> >
>> > I noticed that when going to my Configuration today,
>> there were new versions of Turba (3.0.15), ingo (2.0.9), and
>> imp (5.0.23)
>> >
>> > I was able to install the ingo module normally and so
>> it upgraded fine.
>> >
>> > However, when trying go install Turba, these errors
>> occur:
>> >
>> > horde/turba requires package "horde/Horde_Exception"
>> (version >= 1.0.0, version <= 2.0.0alpha1, excluded
>> versions: 2.0.0alpha1), installed version is 2.0.0beta1
>> > horde/turba requires package "horde/Horde_Support"
>> (version >= 1.0.0, version <= 2.0.0alpha1, excluded
>> versions: 2.0.0alpha1), installed version is 2.0.0beta1
>> > horde/turba requires package "horde/Horde_Url" (version
>> >= 1.0.0, version <= 2.0.0alpha1, excluded versions:
>> 2.0.0alpha1), installed version is 2.0.0beta1
>> > horde/turba can optionally use package
>> "horde/Horde_Ldap" (version >= 1.1.0, version <=
>> 2.0.0alpha1, excluded versions: 2.0.0alpha1)
>> > No valid packages found
>> > upgrade failed
>> >
>> > When trying to upgrade imp, these errors occur:
>> >
>> > horde/imp requires package "horde/Horde_Exception"
>> (version >= 1.0.0, version <= 2.0.0alpha1, excluded
>> versions: 2.0.0alpha1), installed version is 2.0.0beta1
>> > horde/imp requires package "horde/Horde_Support"
>> (version >= 1.0.0, version <= 2.0.0alpha1, excluded
>> versions: 2.0.0alpha1), installed version is 2.0.0beta1
>> > horde/imp requires package "horde/Horde_Url" (version
>> >= 1.0.0, version <= 2.0.0alpha1, excluded versions:
>> 2.0.0alpha1), installed version is 2.0.0beta1
>> > horde/Horde_Imap_Client requires package
>> "horde/Horde_Exception" (version >= 1.0.0, version <=
>> 2.0.0alpha1, excluded versions: 2.0.0alpha1), installed
>> version is 2.0.0beta1
>> > horde/Horde_Imap_Client requires package
>> "horde/Horde_Secret" (version >= 1.0.0, version <=
>> 2.0.0alpha1, excluded versions: 2.0.0alpha1), installed
>> version is 2.0.0beta1
>> > horde/Horde_Imap_Client requires package
>> "horde/Horde_Stream_Filter" (version >= 1.0.0, version
>> <= 2.0.0alpha1, excluded versions: 2.0.0alpha1),
>> installed version is 2.0.0beta1
>> > No valid packages found
>> > upgrade failed
>> >
>> >
>> > There appear to be dependency issues that I don't
>> understand.  How is it that I have webmail installed
>> with the beta versions of the dependencies above - but the
>> newer modules want the alpha version or lower?
>> >
>> > If I change the preferred_state for pear back to alpha,
>> and do the upgrade-all (or upgrade horde/turba and upgrade
>> horde/imp), a different error occurs:
>> >
>> > Duplicate package
>> channel://pear.horde.org/Horde_Auth-2.0.0alpha1 found
>> > Duplicate package
>> channel://pear.horde.org/Horde_Auth-2.0.0beta1 found
>> > upgrade failed
>> >
>> > Any help would be appreciate.  Not sure if there
>> is a conflict with trying to update to the latest versions
>> of H4 with H5 now in the works.
>>
>> Looks like at least part of the install was upgraded to
>> Horde 5 already. The two are not compatible.
>>
>> --mike
>>
>
> Thank you for the reply Mike.  No idea how any part of this could  
> have been upgraded to Horde 5.  Yesterday I simply ran 'upgrade  
> horde/ingo' to update that portion - to fix that issue where all  
> e-mails in the inbox were being deleted upon rules being run.

My guess is that you had preferred state in PEAR set to beta. So when  
you ran the update once the beta releases were out, those were updated  
to Horde 5.
-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org