How can this be fixed to not happen in the future? There should be an upgrade path for the config, and in the worst case just automatically a backup be made, right? Also the LDAP config needs to be preserved (I presume it should already, maybe that’s a bug)?
Can you please file these issues in the tracker at http://github.com/owncloud/core/issues – that way we can not only help single people via the mailing list, but fix it for everyone. Thanks! On Thu, Nov 15, 2012 at 2:00 PM, chymian <[email protected]> wrote: > Am 15.11.2012 13:48, schrieb Mark Ziegler: >> Am 15.11.2012 13:28, schrieb chymian: >>> propbably, there came a new config with the update, which destroyed >>> the old one. and the updater did not make any backup of the config file. >>> WTF! >>> >>> I'm not very happy with this!!! >> Who would be happy? But I am sure you made a backup before, so no need >> to be rude ;-) > > your right, I'm sorry about the WTF! > > but software, which destroys itself is not very nice either! and > produces a lot of work and debugging at the admin side. > and should definitely be marked as alpha-state! > > [rant on] > as I'm used to debian-state of quality, this is very unusual behavior. > but that seems to be normal with KDE! > sorry, I'm a bit pissed > [rant off] > > günter >> >> Mark >> >> _______________________________________________ >> Owncloud mailing list >> [email protected] >> https://mail.kde.org/mailman/listinfo/owncloud > > _______________________________________________ > Owncloud mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/owncloud _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
