Well, where does time go?
Slow progress with people on holiday, tending to rellies etc.
So quick status check.
Major milestone earlier when Trevor finally managed to a get the Koji build system to throw up an ISO!
OK - it was a non-runner with no SME packages, but it WAS an ISO and that was key, and a major milestone.
I can't impress on people just how much time this has taken Trevor.
The rest of the build system is pottering along - currently we don't have 'official' rpm repos but we will in due course.
As JP said recently:
As some might know we left an old plague bases buildsystem with a lot of internal scripts to make the magic happen, to a koji based system like fedora.
We had then to work out:
- naming convention
- hierarchy of build repo
- auto signing
- populate distribution repo
Still on the todo list:
- auto import upstream needed rpm (rocky, epel, openfusion, rpmfusion)
- building iso inside koji (we used a home script) - Close but no cigar yet!
- mount the distribution repos to a final published url
Brian has been chiselling away at the new server-manager. Impressive stuff but there are a few caching issues that are messing about. It's the small things take up so much time.
I actually managed to catch and fix and LDAP bug in the new ldap backend so feeling smug there
Even the incompetents like me can do things...... I am definitely NOT a coder!
We think there may be quite a few servers with 'out of sync' user data possibly caused by bugs from a long time ago. To make your life easy SME does a really tricky dance between unix, smb and ldap passwords, and it is easy for the whole mess to get out of whack. I have at least one - and we need to try and write some code to test for that. <sigh>
JP also said:
Also as John pointed out we are still refining the internal of SME 11.
Postfix instead of qmail
Letsencrypt as core
Bind instead of djbdns
These are the big rocks in progress or remaining. They are not mandatory to get an alpha 1 iso but they are not blocked while waiting for an iso. Both work are being done in parallel.
For SME 12 based on Rocky 9 all this work will be behind us.
So we *hope* that before much longer we can have some sort of ISO to play with, (but it will be a test bench while we do some of the other parts - it will NOT be upgradable because we won't be writing migrate scripts for qmail - postfix etc.). That sort of thing will happen on install/restore once only
But note that some of us have had basic test bench v11s running happily for a while now. I even have a 'restored from back' up version running so we are getting closer.
Clearly anyone who can help us in any way, no matter how small, is always welcome to come and chat with us. We don't bite (usually!) and most of have really poor sense of humour. But we get along!!
Documentation writers and tester particularly welcome!
Just ping me if you want to come and help.
Vaguely how to install - VMs ONLY. You may need to come and talk to us to get it running as there are a few tricks and we may have them all documented (did I mention documentation?):
https://wiki.koozali.org/Sme11BuildQueue#Bare_install_testBug matrix here:
https://bugs.koozali.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+11.X&format=table&action=wrapBugs to verify - pick one and see if you can find it and if it is fixed:
https://bugs.koozali.org/buglist.cgi?action=wrap&product=SME%20Server%2011.X&target_milestone=11.alpha1&bug_status=RESOLVEDBugs to fix (fugly list):
https://bugs.koozali.org/buglist.cgi?action=wrap&product=SME%20Server%2011.X&target_milestone=11.alpha1&bug_status=CONFIRMEDMeanwhile, don't wait for someone else to do the work. Open source is a collective responsibility. The more that help the faster it will get built.
If all else fails then send us cash via a subscription to keep the servers running.
Thanks.