>>1) but it's showing three times the "starting the update process" line, which >>looks strange >>2) but on the fproxy homepage the warning "A new stable version of Freenet is >>available" does not disappear anymore >>3) there's no feedback to the user that the node won't update because there's >>no wrapper. perhaps the whole update mechanism should not be shown to the >>user but a "you could have updated if you had run freenet within the wrapper" > >4) the node does not check for further new versions: > >Freenet 0.7 Build #924 r at custom@ >Freenet-ext Build #5 r9584 >A newer version is available! (Build #927) > >but it's still stuck with the update to #925
5) "It seems that your node isn't running the latest version of the software. Updating to 925 is advised. Your node is currently doing a final check to verify the security of the update. (4/3)" -- huh? step 4 of 3? sorry for the many posts but the problems keep on coming ;)