[horde] Trouble with horde-translation after upgrade to Horde 5.2.18

[Jens Wahnes]

After upgrading to Horde 5.2.18 and the other packages released 
recently, I seem to be having trouble with the horde-translation helper 
application, which is part of the Horde package.

For one, it now seems to use Horde_Yaml without having a dependency on 
it. While this is easy to fix (yet somewhat strange for a point release 
to pull in new dependencies), I still cannot run horde-translation even 
after "pear install horde/Horde_Yaml". It complains about not being able 
to open a ".horde.yml" file:

---------------------------
Horde translation generator
---------------------------
Loading libraries...
[   OK   ] Console_Getopt found.
[   OK   ] Console_Table found.
[   OK   ] File_Find found.

Searching gettext binaries...
[   OK   ] gettext found: /bin/gettext
[   OK   ] msgattrib found: /usr/bin/msgattrib
[   OK   ] msgcat found: /usr/bin/msgcat
[   OK   ] msgcomm found: /usr/bin/msgcomm
[   OK   ] msgfmt found: /usr/bin/msgfmt
[   OK   ] msginit found: /usr/bin/msginit
[   OK   ] msgmerge found: /usr/bin/msgmerge
[   OK   ] xgettext found: /usr/bin/xgettext

[   OK   ] gettext version: 0.17

Searching Horde modules in /[...]/lib/..

   Fatal Error:
   Failed to open file:
      fopen(/[...]/lib/../.horde.yml): failed to open
      stream: No such file or directory
   In /usr/share/pear/Horde/Yaml.php on line 105

   1. Horde_Translation_Script->search_modules()
      /usr/bin/horde-translation:1682
   2. Horde_Translation_Script->strip_horde() /usr/bin/horde-translation:391
   3. array_map() /usr/bin/horde-translation:405
   4. Horde_Translation_Script->strip_horde()
   5. Horde_Yaml::loadFile() /usr/bin/horde-translation:407


It seems that I can still do what I need to do (generate MO files for 
all translation files that I fiddle with locally) when calling the old 
version of horde-translation.  I don't use the Git stuff that replaced 
CVS stuff which was present in the older version of horde-translation, 
so that this workaround is OK for me, but of course I'd prefer to use a 
version that is shipped with a current Horde package.

Is it intentional that Horde_Yaml is now being used?  Or maybe just some 
version of horde-translation intented for Horde 6 slipped into the Horde 
5 tree?  I haven't seen a ".horde.yml" file anywhere (it's not part of 
what "pear list-files horde/Horde" shows), so I really don't know where 
this file would come from.  What's the best way to deal with this situation?


Jens