[horde] [SOLVED] install from GIT -> migration issues

[Jan Schneider]

Zitat von Joerg Pulz <Joerg.Pulz at frm2.tum.de>:

> ----- Message from Jan Schneider <jan at horde.org> ---------
>    Date: Fri, 16 Aug 2013 11:02:01 +0200
>    From: Jan Schneider <jan at horde.org>
> Subject: Re: [horde] install from GIT -> migration issues
>      To: horde at lists.horde.org
>
>> Zitat von Joerg Pulz <Joerg.Pulz at frm2.tum.de>:
>>
>>> Dear list,
>>>
>>> i've installed horde from git, following exactly the official  
>>> documentation for it.
>>> I've configured everything and it is running very smooth.
>>>
>>> After another 'git pull' i noticed several new migration scripts  
>>> for framework packages (e.g. History).
>>> I did a 'php ./install_dev' checked that "$app_fileroot" is set  
>>> correctly in the destinations 'config/registry.php'.
>>> Running 'bin/horde-db-migrate' in the destination folder has  
>>> checked/updated DB schemas for all horde applications but not for  
>>> framework packages.
>>> It shows that only horde applications can be updated.
>>> Looking in the configuration Web UI shows only the installed horde  
>>> applications but no framework packages.
>>>
>>> Looking around in the destination folder shows, that no  
>>> 'migration' directories have been linked/copied by running 'php  
>>> ./install_dev' in the git checkout folder. How should  
>>> horde-db-migrate work if there is no migration folder for  
>>> framework packages?
>>
>> It's looking at the original location for the migration folders,  
>> i.e. in the checkout folder, not at the link location.
>>
>>> Manually linking/copying the migration directories from git folder  
>>> to the web accessible folder changes nothing. Explicitly  
>>> specifying the migration directory doesn't work either and results  
>>> in "/path/to/framework/migration/dir is neither a configured Horde  
>>> application nor a migration directory". How is horde-db-migrate  
>>> checking for registered framework packages? They are not specified  
>>> in registry.php as they are framework packages, and not  
>>> applications.
>>>
>>> Is there something missing on my side?
>>
>> Are you running horde-db-migrate directly in the checkout  
>> directory? This should work.
>>
>>> As far as i understand the git install docs, there should be  
>>> nothing more to do than evereything i have already done. Is there  
>>> a magic undocumented command to register the framework packages so  
>>> that they are known to horde-db-migrate?
>>
>> No, it should work out of the box, as this is the setup that every  
>> Horde developer is using on a daily basis.
>
> ----- End message from Jan Schneider <jan at horde.org> -----
>
> Jan,
>
> i tried it from the checkout and the destination directory and it  
> didn't work from any of them.
>
> After tracing the system calls during execution of  
> 'horde-db-migrate' i finally found my problem.
> All framework packages are found and the various package.xml files  
> are opened but somehow found not valid and therefor ignored.
> After registering the Horde PEAR channel (hadn't done this before as  
> it was not documented and i've seen no need to do so) the various  
> framework package.xml files are now found valid and the DB migration  
> process for framework packages succeeded.
>
> Please update the documentation.
>
> Kind regards
> Joerg
> This

Done.
-- 
Jan Schneider
The Horde Project
http://www.horde.org/