Wrong Date

[Substring]

please test setting updates.type=gitlab/82-can-t-set-timezone in recalbox.conf. Still, i think the upgrade will fail because tar will have to replace an existing file with a symlink. If so, juste remove /etc/timezone and /etc/localtime and rerun the update.

Once tested and confirm, you can switch back to the normal unstable (and eventually redelete the 2 files before updating)

[Substring]

this is a test branch, so that you confirm the modifications worked. If you calidate, i'll push them to the next unstable release

[cagiraudo]

@Substring said in Wrong Date:

so that you confirm the modifications worked. If you calidate, i'll push them to the next unstable release

ok, sorry i was afk, i will test the fix today and let you know.

Thanks

[Substring]

@cagiraudo ok. Please enclose the logs in the ~/update folder (or by network \\recalbox\share\system\update)

[cagiraudo]

@Substring I just updated it but saddly it still tells me wrong date:

date
Mon Dec 31 22:01:20 ART 1979

Wich logs do you want? i dont have a folder ~/update

[Substring]

@cagiraudo ~/updateis the folder you'd name in SSH. I gave the network full name if you try to reach it with your explorer from windows

anyway i'm pretty sure about the error : /etc/timezone and /etc/localtime used to be some files, and now they are some symbolic links. This should cause trouble on update

[cagiraudo]

@Substring i didn't deleted those files before the update, do you want me to try again deleting thouse files?

[Substring]

@cagiraudo Well ... @azvarel confirmed it works once you delete the 2 files. But that's not a good way to let thousands of users update

[cagiraudo]

@Substring you are right, i will try it anyway to confirm that it's the same problem

[azvarel]

@cagiraudo delete the files before the update, update the updates.type=gitlab/82-can-t-set-timezone in recalbox.conf and change the timezone per manager, you will see that it works.

[cagiraudo]

Ok @azvarel I will try it in a phew hours. Thanks

[cagiraudo]

@azvarel @Substring Should i update again to unstable 4.1 and then to the gitlab/82-can-t-set-timezone or deleting the files will work since i am already in the test branch?

[azvarel]

@cagiraudo atualiza para unstable 4.1, after update, delete the files, then upgrade to gitlab... will work.

[cagiraudo]

Hi again @azvarel @Substring

I can't update to 4.1, i change the source to unstable but i can't finish the update.
I get this error:

[Substring]

@cagiraudo try again until it succeeds

[cagiraudo]

@Substring Ok, i tryied 4 times yesteraday, i will try again tonight

[cagiraudo]

@Substring i tried 10 times yesterday and the same error.

Maybe i can't back to the unstable becouse i am in a branch?? Or something else, but i can't update again

[Substring]

@cagiraudo no you can switch back to unstable (and not gitlab/unstable). I manually tried to download ths file, had no problems.

Have you tried to download it from your webbrowser ?

[cagiraudo]

@Substring im in work, here i could download from the webbrowser without problem, i will try in my home later. If i can download it, is there any way i copy it directly to some folder so i can make the update??

[Substring]

@cagiraudo you need i think 5 files to make an update : root and boot.tar.gz, their sha1 file each, and the root.list. no recalbox at hand now, so i can't say for sure