Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updater tries to skip major versions (8.0) #210

Closed
varesa opened this issue Dec 30, 2015 · 6 comments
Closed

Updater tries to skip major versions (8.0) #210

varesa opened this issue Dec 30, 2015 · 6 comments

Comments

@varesa
Copy link

varesa commented Dec 30, 2015

I was running a 8.0.4 instance and got a nice notification to upgrade to 8.2. I tried running the wizard but it failed since 8.0 -> 8.2 is an invalid upgrade path.

I'm not sure if this is fixed in a later version but the updater should not try to skip major versions.

@ghost
Copy link

ghost commented Dec 31, 2015

Nothing what can be done on updater app side. See owncloud/appstore-issues#4

@ghost
Copy link

ghost commented Dec 31, 2015

See also this duplicate: #30

@varesa varesa closed this as completed Dec 31, 2015
@nalt
Copy link

nalt commented Feb 10, 2016

@RealRancor: Why is there nothing that can be done on the updater app? I would say it is certainly a bug in the updater if it propses an operation which will inevitably fail. #4 has been open for a long time now, so maybe it is simpler to do a check in the updater app.

@ghost
Copy link

ghost commented Feb 10, 2016

@nalt

No. Supporting this means storing a list of all owncloud packages already released somewhere.
That's why owncloud/appstore-issues#4 was opened more than a year ago.
Feed should not propose a package that is not suitable for update (imho).

from owncloud/core#22129 (comment) describes this quite good.

@nalt
Copy link

nalt commented Feb 10, 2016

I agree, the feed should not propose incompatible versions. So, until that happens, let's just call self_destroy() in our update routine ;-)

@VicDeo
Copy link
Member

VicDeo commented Feb 16, 2016

New update server is waiting to be merged. (in another repo). It will deliver compatible versions only.

I came to updater-specific solution not long time ago but it is not straightaway so I'm happy that the issue will be resolved on a proper side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants