View Single Post
Old 03-10-2014, 05:22 AM   #24
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
Quote:
Originally Posted by TechniSol View Post
I strongly suspect that Kobo is depending on users installing incremental updates to get all their ducks in a row when they should be making sure all dependencies are present in each firmware since there is no guarantee of what firmware users started at and apparently not a very good mechanism in place to force necessary intermediate upgrades.(Wow, that's a long sentence...)
After playing around a little with the update request, I am rather inclined to think that this is not the case. For instance, when you upgrade a Glo (Kobo as affiliation) from 3.1.1, Kobo delivers directly the link to the 3.2.0 file. And the same happens, when you upgrade from 2.6.1. Having to go through the upgrade twice might maybe related to a broken download.

Last edited by tshering; 03-10-2014 at 09:32 AM.
tshering is offline   Reply With Quote