2.0.2.43 bug, suggests 2.0.1.11 as update [answered]
asked 2016-06-20 09:43:49 +0200
after updating jolla to 2.0.2.43 it found new update which was 2.0.1.11
The question has been closed for the following reason "the question is answered, an answer was accepted" by mosen
1 Answer
answered 2016-06-20 09:56:53 +0200
Not really a bug, you updated to a non official release, still in testing. Just showing most recent official public release. Version --dup may fix, otherwise ignore "update"
Stats
Asked: 2016-06-20 09:43:49 +0200
Seen: 711 times
Last updated: Jun 20 '16
And what did you expect? 2.0.2 is not out yet officially, is it? Not even for early adopters.
pichlo ( 2016-06-20 09:58:03 +0200 )editMore interesting is how did you find the update? And why didn't you wait till the official release? Do you have problems with the current version?
PatsJolla ( 2016-06-20 10:18:10 +0200 )edit@pichlo, yes I assumed it would see 2.0.2.43 as new version althought it not official. @PatsJolla. Yep, was allready looking out for new phone, just incase.
u can find instructions how to, here on tjc,probably still on frontpage
so far works like a charm :)
FOMBE ( 2016-06-20 10:36:07 +0200 )edit@PatsJolla, this is how.
As for why, well, a number of factors I suppose. The first and foremost is probably impatience. The promised but never really materialized monthly updates must also have contributed. For the developers it might be useful to know what is coming. And, you know, some people like living on the edge ;)
pichlo ( 2016-06-20 10:48:22 +0200 )editgeez, but -6 is not what i expected from our otherwise noobfriendly community... Why don't you express your schadenfreude by keeping it at a screaming zero ;) The question is a valid result of giving an unexperienced user advanced tools and is answered accordingly by @greendts.
mosen ( 2016-06-20 20:28:01 +0200 )edit