Fri, 10 Apr 2026 09:35:54 +0000 https://bugs.horde.org/ticket/8607 problem after update: */config/* files got replicated addictions the first run of scripts/setup.php reported the impossibility to copy /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. Mon, 28 Sep 2009 10:08:41 +0000 https://bugs.horde.org/ticket/8607#t55991 And you upgraded from which version? Can you paste the output and your input on the command line here? > the problem is that some files in the config/ folders got more than > one set of update sections. After you ran the upgrade again? That's not surprising. The upgrade only works on a clean installation. Mon, 26 Oct 2009 14:23:09 +0000 https://bugs.horde.org/ticket/8607#t56398 I upgraded from 1.0.4 to 1.2.4 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. > And you upgraded from which version? Can you paste the output and > your input on the command line here? > >> the problem is that some files in the config/ folders got more than >> one set of update sections. > > After you ran the upgrade again? That's not surprising. The upgrade > only works on a clean installation. Mon, 26 Oct 2009 15:30:38 +0000 https://bugs.horde.org/ticket/8607#t56404 Well, there is not much we can do, if you don't have a system to reproduce this anymore. Mon, 26 Oct 2009 15:50:58 +0000 https://bugs.horde.org/ticket/8607#t56406 well, next week i'll try to upgrade from 1.2.2 to 1.2.4 on another server. 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 Mon, 26 Oct 2009 16:55:27 +0000 https://bugs.horde.org/ticket/8607#t56408