Zitat von Terry Carmen :
On 10/30/2012 10:51 AM, wro...@pardus.de wrote:
Zitat von Lukas Gradl :
Hi!
I did a "pear upgrade" on my IMP 6.0.0 test machine. Afterwards
backends.php was overwritten.
AFAIK the config files should be preserved when upgrading -
should'nt there be a backends
On 10/30/2012 10:51 AM, wro...@pardus.de wrote:
Zitat von Lukas Gradl :
Hi!
I did a "pear upgrade" on my IMP 6.0.0 test machine. Afterwards
backends.php was overwritten.
AFAIK the config files should be preserved when upgrading - should'nt
there be a backends.php.dist that ist updated aut
Am 2012-10-30 15:45, schrieb Oscar del Rio:
On 10/30/12 10:31 AM, Lukas Gradl wrote:
I did a "pear upgrade" on my IMP 6.0.0 test machine. Afterwards
backends.php was overwritten.
AFAIK the config files should be preserved when upgrading - should'nt
there be a backends.php.dist that ist updated a
On 10/30/12 10:31 AM, Lukas Gradl wrote:
I did a "pear upgrade" on my IMP 6.0.0 test machine. Afterwards
backends.php was overwritten.
AFAIK the config files should be preserved when upgrading - should'nt
there be a backends.php.dist that ist updated automatically and the
active copy should'nt
Zitat von Lukas Gradl :
Hi!
I did a "pear upgrade" on my IMP 6.0.0 test machine. Afterwards
backends.php was overwritten.
AFAIK the config files should be preserved when upgrading -
should'nt there be a backends.php.dist that ist updated
automatically and the active copy should'nt be t
Hi!
I did a "pear upgrade" on my IMP 6.0.0 test machine. Afterwards
backends.php was overwritten.
AFAIK the config files should be preserved when upgrading - should'nt
there be a backends.php.dist that ist updated automatically and the
active copy should'nt be touched?
regards
Lukas
--
imp