Summary | problem after update: */config/* files got replicated addictions |
Queue | Horde Groupware Webmail Edition |
Queue Version | 1.2.4 |
Type | Bug |
State | No Feedback |
Priority | 1. Low |
Owners | |
Requester | scaramuzza (at) essedici (dot) it |
Created | 09/28/2009 (5793 days ago) |
Due | 09/28/2009 (5793 days ago) |
Updated | 10/26/2009 (5765 days ago) |
Assigned | 10/26/2009 (5765 days ago) |
Resolved | 10/26/2009 (5765 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
I signaled the anomaly that incurred to me just to let you know. i
hoped it could be a simple bug in the setup script that somebody could
quickly identify.
best regards
federico
State ⇒ No Feedback
reproduce this anymore.
I've no more any copy of my upgrade session, i've just my notes on my
"installation and configuration log". There I read that a first
execution of ./scripts/setup.php reported
the impossibility to to the upgrade.
After my manual creation of the symlink, as reported, I did a second
run of ./scripts/setup.php.
The second run ended without any error message (I examined all the
lines printed on the console).
After the second (and only successful run) I got 41 repeated blocks of
the same upgrade code (one example is attached).
I did no more run of the setup/upgrade script and manually corrected
each bloated */config/*.php
Now Horde 1.2.4 runs perfectly (given the correction in
http://bugs.horde.org/ticket/8615).
best regards
f.
your input on the command line here?
one set of update sections.
only works on a clean installation.
State ⇒ Feedback
input on the command line here?
one set of update sections.
only works on a clean installation.
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ problem after update: */config/* files got replicated addictions
Due ⇒ 09/28/2009
Queue ⇒ Horde Groupware Webmail Edition
Milestone ⇒
Patch ⇒ No
New Attachment: kronolith.prefs.php.wrong
State ⇒ Unconfirmed
/OLDRELEASE/config/prefs.php to /NEWRELEASE/../horde/config/prefs.php
(note that the path signaled was correct and does not contain /horde/)
so i created a symlink in /NEWRELEASE/ (ln -s . horde) and the update
procedure completed without any error.
the problem is that some files in the config/ folders got more than
one set of update sections.
attached you can find one of the files i had to manually correct.