hi, Am 15.11.2012 16:57, schrieb Victor Dubiniuk: > Hi, > > at the first place many thanks for your feedback. > > > If users are getting angry it is not a good sign, but people need to > test it first. > Even debian quality software needs testing on a test machine or a > test environment before you run an upgrade. > running a upgrade over an installation without testing could get you > in trouble. > > /* Offtopic */ > I had been installing a network printer yesterday and decided to give > hplip a try. This morning I found that I have no WebGL acceleration > anymore and unable to start VirtualBox and some other applications. > I was cool as a stone while troubleshooting it and adding my user back > to the groups he had had before. As the installer left only those > required to manage printing. :) > /* End of Offtopic */
/* offtopic */ what lead to my relatively uncalm mood was: after I realized, that thunderbird is not updating subscribed imap feeds as it should, and sogo in combination with IOS 4.2 is deleting adr-cards totally unmotivated and out of the blue, I gave KDEPIM a try again, this time trying to connect it to owncloud, instead of sogo. KDE works with KDE – was the idea (despite all the 4.x story, users had to swallow). but since kontact is still on 4.4 within debian – due to a major bug, which the debian-pack.team found – it failed miserably to connect to any of both card-/cal-dav server (sogo & OC). than updating OC ruined the installation..., well, one of these days in an admin's daily life – I think. sorry again for being rude. /* end of story */ thx for your patience and all your work :) günter > > As for the Updater, testing under various circumstances took 60-70% of > its development last month. > > On Thu, Nov 15, 2012 at 6:12 PM, Michael <[email protected] > <mailto:[email protected]>> wrote: > > Maybe a warning with a link on making a backup and how important it is? > > > Whatever application I update on the production servers I make a working > snapshot of the previous version first. It's a matter of seconds to > change docroot or create a symlink if something goes wrong. > Even if upgrade is successful there might be a serious reasons for > rolling back to the previous version. > > Updater performs full instance backup (excluding database and data > directory). There are no files missed. If it is not possible to create a > backup it stops on the first stage with the message 'Unable to create > backup' > > I'll implement some advanced features very soon. v0.2.5 is a basis that > allows various checks before starting the upgrade process. The very > first thing I will implement is sending zipped backup via email. > another one is the checkbox 'I agree that it may be the last time I see > the following apps:' followed by the list of apps that are not > compatible with a new core. > > --- > Victor > > > On Thu, Nov 15, 2012 at 8:47 AM, Johan Hendriks > <[email protected] <mailto:[email protected]>> wrote: > > Just a thank you for all the work. > > I think owncloud is doing well, but it needs to mature a bit more. > Mature in the department off releasing, documentation and so on. > If things settle down in the future there is more time to do > more testing. > > If users are getting angry it is not a good sign, but people > need to test it first. > Even debian quality software needs testing on a test machine or > a test environment before you run an upgrade. > running a upgrade over an installation without testing could get > you in trouble. > > Well we all learned something :D > > gr > Johan > > > > > > > > Victor Dubiniuk schreef: >> Hi Günter, >> >> I spent some time writing README. It is available in the app >> directory and on the >> github https://github.com/owncloud/apps/tree/master/updater >> In short: >> - If it is not possible to create a valid backup of the files >> the upgrade process won't proceed; >> - Database connection detail are stored inside *config.php*. >> It is not deleted on upgrade; >> - All the files of the previous instance are stored inside >> your backup.; >> - Many 3rdparty apps won't work with the new version anyway >> since they have maximal core version they are compatible with. >> So there is no reason to leave them, moreover it may cause >> various issues right after upgrade; >> - There are good chances not to have 3rd party apps compatible >> with X.Y.Z in the same day X.Y.Z is released; >> - I have a full-time job and family and I spend evenings >> upgrading different versions of numerous ownCloud instances in >> order to make the upgrade process smooth enough. >> >> Please accept my apologies for all the inconveniences you had. >> >> --- >> Victor >> >> On Thu, Nov 15, 2012 at 4:14 PM, Jan-Christoph Borchardt >> <[email protected] <mailto:[email protected]>> wrote: >> >> 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] >> <mailto:[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] <mailto:[email protected]> >> >> https://mail.kde.org/mailman/listinfo/owncloud >> > >> > _______________________________________________ >> > Owncloud mailing list >> > [email protected] <mailto:[email protected]> >> > https://mail.kde.org/mailman/listinfo/owncloud >> _______________________________________________ >> Owncloud mailing list >> [email protected] <mailto:[email protected]> >> https://mail.kde.org/mailman/listinfo/owncloud >> >> >> >> >> _______________________________________________ >> Owncloud mailing list >> [email protected] <mailto:[email protected]> >> https://mail.kde.org/mailman/listinfo/owncloud > > > _______________________________________________ > Owncloud mailing list > [email protected] <mailto:[email protected]> > https://mail.kde.org/mailman/listinfo/owncloud > > > > _______________________________________________ > Owncloud mailing list > [email protected] <mailto:[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
