There would be a brief downtime when taking snapshot of the server. We will be upgrading the Operating System on auth.librem.one to a newer version. All Librem One services use auth.librem.one to authenticate users, so during this maintenance, you won’t be able to login/create new sessions on any Librem One services.
3 Likes
Will this also lay the foundation for fixing payment plans on Librem One?
1 Like
This is a routine update. For fixes to specific issues, we will need to engage developers.
2 Likes
That should be abouts just after midnight for U.S. east coast and late evening for West Coast. I will try not to expect any midnight emails.
2 Likes
I was told the billing would be ready around the end of March, is that still the current timescale for Librem One billing? I would love to pay the premium “gotta have it all” $7.99 plan so that I can use the Librem Tunnel and Librem Mail features of Librem One.
1 Like
I suggest you contact support.
1 Like
I will contact them again. Hopefully they have another update for me. They’d last told me that it would be this month.
1 Like
This update is complete. We are not on the latest version of OS yet, so I will schedule another maintenance soon for next upgrade.
Total down time was a few minutes for backup and reboot.
3 Likes
Next update will be on 27th at 6am UTC, similar to this update a few minutes of downtime is expected.
2 Likes
This update is completed with a few minutes of downtime. Since we are still one release behind from the latest, expect another maintenance soon.
1 Like
The next update is actually blocked on debian packaging mentions license as GPL but source code is not provided · Issue #90 · fusiondirectory/fusiondirectory · GitHub Basically we use fusion directory for web based management of our LDAP/user directory instance (for both Librem.One and Puri.sm). Fusion Directory upstream developers started withholding the source packages after debian bullseye release and it was removed from Debian archives since its package maintainer did not want to reverse engineer the build system from the binary packages.
Their official repository only provides binary packages and they don’t provide any documentation or other build system to install it from source. Initially we tried looking for alternatives, but it looks like they withholding source packages is a violation of GPL as they are not the only copyright holders for fusion directory and debian packaging is a derivative work of fusion directory. Any derivative work should also be under GPL and any software under GPL must provide its corresponding source code.
I also tried to install from source repo, but without any documentation or support it is impossible to install from source repo.
We need to resolve this issue before we can update the OS to bookworm - the old version (fusion directory 1.3) no longer works on Debian Bookworm because it is not compatible with the new PHP version 8.2 in Bookworm.
It’d be good if people can validate my findings and comment on the linked issue.
2 Likes