View Issue Details

This bug affects 1 person(s).
 6
IDProjectCategoryView StatusLast Update
12124Bug reportsComfortUpdatepublic2017-10-23 11:09
Reporterpmonstad Assigned ToLouisGac 
PrioritynoneSeveritycrash 
Status closedResolutionfixed 
Product Version2.62.x 
Summary12124: not able to run ComfortUpdate: build_not_found
Description

Not possible to run ComfortUpdate. I get an error telling build_not_found

The installation build is 170303! Could this be the problem? The build is ahead in time?

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build)170303
I will donate to the project if issue is resolvedNo
Browserall
Database type & versionall
Server OS (if known)all
Webserver software & version (if known)all
PHP Versionall

Users monitoring this issue

There are no users monitoring this issue.

Activities

jelo

jelo

2017-02-10 16:20

partner   ~42996

Did you update to 170303 before via comfortupdate? I saw a post in the forum with 170303 and thought it was a mistype by the poster. I currently being offered the update 2.62.2 (170203) via comfortupdate.
So you could be right, that the build version check routine isn't allowing a downgrade.

pmonstad

pmonstad

2017-02-10 17:39

updater   ~42997

Yes, I updated to 170303 via ComfortUpdate from the latest release before 170303. The version number is wrong and most likely the problem here...

celticalliance

celticalliance

2017-02-11 13:05

reporter   ~42998

Yeah, that would have been me :) I already found it strange that the buildnumber was 170303, but now I can't use ComfortUpdate to check for updates.

Logging into LimeSurvey works fine btw.

celticalliance

celticalliance

2017-02-11 13:07

reporter   ~42999

Do you guys know of any way to fix this?

celticalliance

celticalliance

2017-02-21 13:16

reporter   ~43041

Today, 21 February 2017, I was able to update to 2.63.1, but the build number now says 170305? However, clicking on the ComfortUpdate button does not throw out the build_not_found error anymore.

Is there a way to fix the incorrect build number? It's rather annoying.

jelo

jelo

2017-02-21 13:24

partner   ~43042

@celticalliance
You were able to update via Comfortupdate cause the buildnumber is in the future.
Fixing the buildnumber by hand will broke it.
Perhaps LS GmbH will fix it later, when the Comfortupdater can handle update which go "back in time".
Since the version scheme was changed, there is no need for the build-date.
Just focus on the version number.

celticalliance

celticalliance

2017-02-21 13:48

reporter   ~43044

Alright. Thank you :)

Issue History

Date Modified Username Field Change
2017-02-10 15:29 pmonstad New Issue
2017-02-10 15:29 pmonstad Status new => assigned
2017-02-10 15:29 pmonstad Assigned To => LouisGac
2017-02-10 16:20 jelo Note Added: 42996
2017-02-10 17:39 pmonstad Note Added: 42997
2017-02-11 13:05 celticalliance Note Added: 42998
2017-02-11 13:07 celticalliance Note Added: 42999
2017-02-21 13:16 celticalliance Note Added: 43041
2017-02-21 13:24 jelo Note Added: 43042
2017-02-21 13:48 celticalliance Note Added: 43044
2017-10-23 11:09 LouisGac Status assigned => closed
2017-10-23 11:09 LouisGac Resolution open => fixed