> Hi! Hi!
> I just updated my Suse server to 2.8, and have had two issues with it: > > -like on my Debian machines, I run a self-compiled Midgard with prefix > set to /usr/local. Unfortunately this always causes "Midgard not > initialized!" errors when doing PEAR upgrades, because it looks for the > config file in /etc/midgard/conf.d, but make install created it in > /usr/local/etc/midgard/conf.d. I worked around this by creating a > symlink, but it would be nice if this could either be auto-detected or > if there was a config option to influence it. Have a look at /usr/local/include/midgard/midgard_config_auto.h and at /usr/include/midgard/midgard_config_auto.h ( if exists ). This file defines your local setup configuration. Either you have midgard installed twice or there's some issue with MIDGARD_LIB_PREFIX defined in this header file. > I got around this by setting MidgardUsername and MidgardPassword in the > config file (although the comments say "You shouldn't use configuration > below in real life"). Mysteriously, this didn't happen on my Debian > machines, because there, the values were already present (but I didn't > set them manually). > So, I don't know if this is an issue with me messing up config files or > if Midgard should somehow take care of this, but at least the comment is > a bit misleading.. Datagard checks if values are correct and set them if needed. Please double check if you do not have midgard installed twice with different prefixes. Piotras _______________________________________________ user mailing list user@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/user
