[prev in list] [next in list] [prev in thread] [next in thread] 

List:       owncloud
Subject:    Re: [Owncloud] updater.php error: Access to undeclared static property: OC::$APPSROOT
From:       Victor Dubiniuk <victor.dubiniuk () gmail ! com>
Date:       2012-11-15 15:57:16
Message-ID: CA+UHsBu69gBfvbEs2pLS2iGz1GpP5rqybtqjhOYWerz6vzs9qw () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi,

at the first place many thanks for your feedback.

On Thu, Nov 15, 2012 at 8:47 AM, Johan Hendriks <joh.hendriks@gmail.com>
 wrote:

> 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 */

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 <mike@draftx.net> 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 <joh.hendriks@gmail.com>wro=
te:
>
>>  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 testin=
g.
>>
>> If users are getting angry it is not a good sign, but people need to tes=
t
>> 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=FCnter,
>>
>>  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 upgrad=
e
>> 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 reaso=
n
>> 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 <
>> hey@jancborchardt.net> 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=92s a bug)?
>>>
>>> Can you please file these issues in the tracker at
>>> http://github.com/owncloud/core/issues =96 that way we can not only hel=
p
>>> single people via the mailing list, but fix it for everyone. Thanks!
>>>
>>>
>>>
>>> On Thu, Nov 15, 2012 at 2:00 PM, chymian <chymian@gmx.net> 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 ne=
ed
>>> >> 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=FCnter
>>> >>
>>> >> Mark
>>> >>
>>> >> _______________________________________________
>>> >> Owncloud mailing list
>>> >> Owncloud@kde.org
>>> >> https://mail.kde.org/mailman/listinfo/owncloud
>>> >
>>> > _______________________________________________
>>> > Owncloud mailing list
>>> > Owncloud@kde.org
>>> > https://mail.kde.org/mailman/listinfo/owncloud
>>> _______________________________________________
>>> Owncloud mailing list
>>> Owncloud@kde.org
>>> https://mail.kde.org/mailman/listinfo/owncloud
>>>
>>
>>
>>
>> _______________________________________________
>> Owncloud mailing listOwncloud@kde.orghttps://mail.kde.org/mailman/listin=
fo/owncloud
>>
>>
>>
>> _______________________________________________
>> Owncloud mailing list
>> Owncloud@kde.org
>> https://mail.kde.org/mailman/listinfo/owncloud
>>
>>
>
> _______________________________________________
> Owncloud mailing list
> Owncloud@kde.org
> https://mail.kde.org/mailman/listinfo/owncloud
>
>

[Attachment #5 (text/html)]

<div>Hi,</div><div><br></div><div>at the first place many thanks for your \
feedback.</div><div><br></div><div>On Thu, Nov 15, 2012 at 8:47 AM, Johan Hendriks <span \
dir="ltr">&lt;<a href="mailto:joh.hendriks@gmail.com" \
target="_blank">joh.hendriks@gmail.com</a>&gt;</span> wrote:</div> <blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">If \
users are getting angry it is not a good sign, but people need to test it first.<br> Even \
debian quality software needs testing on a test machine or a test environment before you run an \
upgrade.<br>running a upgrade over an installation without testing could get you in \
trouble.</blockquote><div>/* Offtopic */</div> <div><div>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.</div> <div>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. :)</div></div><div>/*  \
End of Offtopic */</div><div> <br></div><div>As for the Updater, testing under various \
circumstances took 60-70% of its development last month.</div><div><br></div><div>On Thu, Nov \
15, 2012 at 6:12 PM, Michael <span dir="ltr">&lt;<a href="mailto:mike@draftx.net" \
target="_blank">mike@draftx.net</a>&gt;</span> wrote: </div> <blockquote class="gmail_quote" \
style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Maybe \
a warning with a link on making a backup and how important it is?</blockquote> \
<div><br></div><div>Whatever application I update on the production servers I make a working \
snapshot of the previous version first. It&#39;s a matter of seconds to change docroot or \
create a symlink if something goes wrong.</div> <div>Even if upgrade is successful there might \
be a serious reasons for rolling back to the previous version.</div><div><br></div><div>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 \
&#39;Unable to create backup&#39;</div> <div><br></div><div>I&#39;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.</div> \
<div>another one is the checkbox &#39;I agree that it may be the last time I see the following \
apps:&#39;  followed by the list of apps that are not compatible with a new \
core.</div><div><br></div><div>---</div><div>Victor</div> <div> </div><br><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><div class="gmail_quote">On \
Thu, Nov 15, 2012 at 8:47 AM, Johan Hendriks <span dir="ltr">&lt;<a \
href="mailto:joh.hendriks@gmail.com" target="_blank">joh.hendriks@gmail.com</a>&gt;</span> \
wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">

  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <div>Just a thank you for all the work.<br>
      <br>
      I think owncloud is doing well, but it needs to mature a bit more.<br>
      Mature in the department off releasing, documentation and so on.<br>
      If things settle down in the future there is more time to do more
      testing.<br>
      <br>
      If users are getting angry it is not a good sign, but people need
      to test it first.<br>
      Even debian quality software needs testing on a test machine or a
      test environment before you run an upgrade.<br>
      running a upgrade over an installation without testing could get
      you in trouble.<br>
      <br>
      Well we all learned something :D<br>
      <br>
      gr<br>
      Johan<br>
      <br>
      <br>
      <br>
      <br>
      <br>
      <br>
      <br>
      Victor Dubiniuk schreef:<br>
    </div><div><div>
    <blockquote type="cite">Hi <span \
style="color:rgb(80,0,80);font-size:13px;font-family:arial,sans-serif">Günter</span>,  \
<div><br>  </div>
      <div>I spent some time writing README. It is available in the app
        directory and on the github <a \
href="https://github.com/owncloud/apps/tree/master/updater" \
target="_blank">https://github.com/owncloud/apps/tree/master/updater</a><br>  In short:</div>
      <div>- If it is not possible to create a valid backup of the files
        the upgrade process won&#39;t proceed;</div>
      <div>- Database connection detail are stored inside <b>config.php</b>.
        It is not deleted on upgrade;</div>
      <div>- All the files of the previous instance are stored inside
        your backup.;</div>
      <div>- Many 3rdparty apps won&#39;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;</div>
      <div>- There are good chances not to have 3rd party
        apps compatible with X.Y.Z in the same day X.Y.Z is released;</div>
      <div>- 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.</div>
      <div><br>
      </div>
      <div>Please accept my apologies for all the inconveniences you
        had.</div>
      <div><br>
        ---</div>
      <div>Victor<br>
        <br>
        <div class="gmail_quote">On Thu, Nov 15, 2012 at 4:14 PM,
          Jan-Christoph Borchardt <span dir="ltr">&lt;<a href="mailto:hey@jancborchardt.net" \
target="_blank">hey@jancborchardt.net</a>&gt;</span>  wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">How can  this be fixed to not happen in the future? There should be
            an<br>
            upgrade path for the config, and in the worst case just
            automatically<br>
            a backup be made, right? Also the LDAP config needs to be
            preserved (I<br>
            presume it should already, maybe that’s a bug)?<br>
            <br>
            Can you please file these issues in the tracker at<br>
            <a href="http://github.com/owncloud/core/issues" \
target="_blank">http://github.com/owncloud/core/issues</a>  – that way we can not only help<br>
            single people via the mailing list, but fix it for everyone.
            Thanks!<br>
            <div>
              <div><br>
                <br>
                <br>
                On Thu, Nov 15, 2012 at 2:00 PM, chymian &lt;<a href="mailto:chymian@gmx.net" \
target="_blank">chymian@gmx.net</a>&gt;  wrote:<br>
                &gt; Am 15.11.2012 13:48, schrieb Mark Ziegler:<br>
                &gt;&gt; Am 15.11.2012 13:28, schrieb chymian:<br>
                &gt;&gt;&gt; propbably, there came a new config with the
                update, which destroyed<br>
                &gt;&gt;&gt; the old one. and the updater did not make
                any backup of the config file.<br>
                &gt;&gt;&gt; WTF!<br>
                &gt;&gt;&gt;<br>
                &gt;&gt;&gt; I&#39;m not very happy with this!!!<br>
                &gt;&gt; Who would be happy? But I am sure you made a
                backup before, so no need<br>
                &gt;&gt; to be rude ;-)<br>
                &gt;<br>
                &gt; your right, I&#39;m sorry about the WTF!<br>
                &gt;<br>
                &gt; but software, which destroys itself is not very
                nice either! and<br>
                &gt; produces a lot of work and debugging at the admin
                side.<br>
                &gt; and should definitely be marked as alpha-state!<br>
                &gt;<br>
                &gt; [rant on]<br>
                &gt; as I&#39;m used to debian-state of quality, this is
                very unusual behavior.<br>
                &gt; but that seems to be normal with KDE!<br>
                &gt; sorry, I&#39;m a bit pissed<br>
                &gt; [rant off]<br>
                &gt;<br>
                &gt; günter<br>
                &gt;&gt;<br>
                &gt;&gt; Mark<br>
                &gt;&gt;<br>
                &gt;&gt; _______________________________________________<br>
                &gt;&gt; Owncloud mailing list<br>
                &gt;&gt; <a href="mailto:Owncloud@kde.org" \
                target="_blank">Owncloud@kde.org</a><br>
                &gt;&gt; <a href="https://mail.kde.org/mailman/listinfo/owncloud" \
target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a><br>  &gt;<br>
                &gt; _______________________________________________<br>
                &gt; Owncloud mailing list<br>
                &gt; <a href="mailto:Owncloud@kde.org" target="_blank">Owncloud@kde.org</a><br>
                &gt; <a href="https://mail.kde.org/mailman/listinfo/owncloud" \
target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a><br>  \
_______________________________________________<br>  Owncloud mailing list<br>
                <a href="mailto:Owncloud@kde.org" target="_blank">Owncloud@kde.org</a><br>
                <a href="https://mail.kde.org/mailman/listinfo/owncloud" \
target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a><br>  </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
Owncloud mailing list
<a href="mailto:Owncloud@kde.org" target="_blank">Owncloud@kde.org</a>
<a href="https://mail.kde.org/mailman/listinfo/owncloud" \
target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a> </pre>
    </blockquote>
    <br>
  </div></div></div>

<br>_______________________________________________<br>
Owncloud mailing list<br>
<a href="mailto:Owncloud@kde.org" target="_blank">Owncloud@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/owncloud" \
target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a><br> \
<br></blockquote></div><br> </div></div><br>_______________________________________________<br>
Owncloud mailing list<br>
<a href="mailto:Owncloud@kde.org">Owncloud@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/owncloud" \
target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a><br> \
<br></blockquote></div><br>



_______________________________________________
Owncloud mailing list
Owncloud@kde.org
https://mail.kde.org/mailman/listinfo/owncloud


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic