Watch out for your system clock , when upgrading.

[bingo600]

Watch out for your system clock , when upgrading.
Somehow (on my PP CE edition) it FSCK's up and TimeWarps to year 2115 , happpend 3 times now.

If the sysclock is that much wrong , then the repos used has expired , and gives an error.

*** Update fails

root@mobian:~# apt update
Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB]
Hit:2 http://repo.mobian-project.org mobian InRelease   
Reading package lists... Done
E: Release file for http://deb.debian.org/debian/dists/bullseye/InRelease is expired (invalid since 34743d 13h 12min 59s). Updates for this repository will not be applied.
root@mobian:~#


*** Check clock = TimeWarp
root@mobian:~# date
2115-10-12T05:35:27 CEST

*** Set sysclock from hw clock
root@mobian:~# hwclock -s

*** Date ok now
root@mobian:~# date
2020-08-19T20:17:43 CEST
root@mobian:~#

*** Update works
root@mobian:~# apt update


Why doesn't the OS do a hwclock -s , during boot ??


/Bingo

---

Well a dist-upgrade , just installed this one :
Get:1 http://deb.debian.org/debian bullseye/main arm64 systemd-timesyncd arm64 246.1-1 [124 kB]

Will that solve the TimeWarp ? , or just keep the clock sync'ed like NTP ?



**** Bonus Q: ****

root@mobian:~# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
mobian-base mobian-phosh-base mobian-phosh-games mobian-phosh-phone
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
root@mobian:~#

1:

I have 4 packages held back:
mobian-base mobian-phosh-base mobian-phosh-games mobian-phosh-phone

Should i install these ??

I'm on latest update/upgrade as of 2020-08-19
root@mobian:~# uname -a
Linux mobian 5.7-pinephone #1 SMP PREEMPT Thu Aug 6 15:47:23 UTC 2020 aarch64 GNU/Linux

2:
How do i install them , if needed ?

3: Are there any specific order to install them ??

TIA
Bingo

[a-wai]

Yes, you should definitely upgrade mobian-* as they will replace systemd-timesyncd with chrony, which is way better at keeping the system clock in sync.
I think 'sudo apt upgrade mobian-base' (maybe followed by another dist-upgrade) should be enough.

[bcnaz]

No 'time' problem when running 'Nightly Build' releases.

Remember to do all the 'region & Language' fill-in the blanks caused this problem before.

[bingo600]

Yes, you should definitely upgrade mobian-* as they will replace systemd-timesyncd with chrony, which is way better at keeping the system clock in sync.
I think 'sudo apt upgrade mobian-base' (maybe followed by another dist-upgrade) should be enough.

Well that : sudo apt upgrade mobian-base
Did not go verry well.

The upgrade went fine , but the following update/upgrade killed the ssh server , and Kings-X showed it hang in dpkg install "some account stuff"

I waited like 20 min , still hanging.

Decided to reboot , but then the phone booted until the "Console screen" where it shown tty01 , and mobian login.
Never started the GUI or showed a keyboard.

I could ping the ip , and connect via ssh.
But never logged in via ssh , as it asked for pwd , but never got further , just hang in the ssh login screen.

I had no alternative but to :
Install the latest nightly on my 32GB SD
Resize the root partition w. gparted to "32GB"
Insert & boot.

I had hoped , NOT to have to do custimizations once more.
Especially because i have  2 WiFi AP's , and mobian does NOT like that (asking for pwd all the time).

I found & imlemented a trick here
https://forum.pine64.org/showthread.php?tid=10966

And have to do that again , plus the "Static MAC" for getting the same DHCP and a bit more stuff.

Well i like the way Mobian is going, and it is 2 month since i last did a full SD reinstall ..

I just need Signal in order to make this my primary phone, is anyone pushing/begging Whisper ???

Thanx goes to all involved developers/resources

/Bingo - Who's off to customize the phone again

[bcnaz]

I understand everything must be set-up again with a 'fresh' install, and that can take some time.
However it will not be as 'patched-up' as an older updated & upgraded install ?
* especially this time, since the clock system has been completely replaced.
But that's just my opinion.