🧪 YunoHost 12.0 alpha (Bookworm)

bjarkan · June 25, 2024, 12:25am

reading almost all the posts… it looks like it’s about a 95% done… but i want to make the unconfortable question… When it will be ready and tested?.. my guess is before chrismas, not that i’m been unoptimistic… just counting that other problems will arrise… may be… fall (october-november), sooner… ?

I do agree that give a time line or an exact date is wrong… but are my guesses right?

Let’s say at the end of august could be named beta instead of alpha… are 3 months enough for have a relative stable product… or just as most debian developers says … when it is ready…

OniriCorpe · June 25, 2024, 2:19am

There’s no ETA, and:

Thread policy : following past traumas, we will not hesitate to remove any comment which do not add anything constructive on making progress with this, such as asking “Any update on this ?”, “What is the ETA ?”, “Bookworm is soon to be released”, “Bookworm has been release for X days zomg 1!?!!”, etc. We are a volunteer team, we will release stuff when it’s stable, and you are welcome to effectively help us getting shit done, but for the love of god don’t pressure volunteers as if they owe you something

Vanitarium · June 25, 2024, 9:06am

Thank you volunteers and testers and developers: Yunohost on Bookworm will rock and be very successful! I shall test on a VM today … Thank you again

Vanitarium · June 25, 2024, 10:57am

Hi,
installed phpsysinfo app and when I run it it returned this error:

phpSysInfo requires the simplexml extension to php in order to work properly.

Can I do something here to help?
I am running Yuno on a UTM VM on macOS

Vanitarium · June 25, 2024, 11:46am

Installing Mattermost I get these lines in History:

Starting a systemd service...
(this may take some time)
The service mattermost didn't fully executed the action start before the timeout.
Please find here an extract of the end of the log of the service mattermost:
Jun 25 12:38:52 mattermost[46974]: {"timestamp":"2024-06-25 12:38:52.930 +01:00","level":"info","msg":"got public IP address for local interface","caller":"app/plugin_api.go:1004","plugin_id":"com.mattermost.calls","origin":"main.(*logger).Info log.go:104","localAddr":"192.168.64.4","remoteAddr":"84.68.73.92"}
Jun 25 12:38:52 mattermost[46974]: {"timestamp":"2024-06-25 12:38:52.931 +01:00","level":"info","msg":"rtc: server is listening on udp 127.0.0.1:8443","caller":"app/plugin_api.go:1004","plugin_id":"com.mattermost.calls","origin":"main.(*logger).Info log.go:104"}
Jun 25 12:38:52 mattermost[46974]: {"timestamp":"2024-06-25 12:38:52.932 +01:00","level":"info","msg":"rtc: server is listening on udp 127.0.0.1:8443","caller":"app/plugin_api.go:1004","plugin_id":"com.mattermost.calls","origin":"main.(*logger).Info log.go:104"}
Jun 25 12:38:52 mattermost[46974]: {"timestamp":"2024-06-25 12:38:52.933 +01:00","level":"info","msg":"rtc: server is listening on udp 127.0.0.1:8443","caller":"app/plugin_api.go:1004","plugin_id":"com.mattermost.calls","origin":"main.(*logger).Info log.go:104"}
Jun 25 12:38:52 mattermost[46974]: {"timestamp":"2024-06-25 12:38:52.935 +01:00","level":"info","msg":"rtc: server is listening on udp 127.0.0.1:8443","caller":"app/plugin_api.go:1004","plugin_id":"com.mattermost.calls","origin":"main.(*logger).Info log.go:104"}
Jun 25 12:38:52 mattermost[46974]: {"timestamp":"2024-06-25 12:38:52.936 +01:00","level":"info","msg":"rtc: server is listening on udp 192.168.64.4:8443","caller":"app/plugin_api.go:1004","plugin_id":"com.mattermost.calls","origin":"main.(*logger).Info log.go:104"}
Jun 25 12:38:52 mattermost[46974]: {"timestamp":"2024-06-25 12:38:52.937 +01:00","level":"info","msg":"rtc: server is listening on udp 192.168.64.4:8443","caller":"app/plugin_api.go:1004","plugin_id":"com.mattermost.calls","origin":"main.(*logger).Info log.go:104"}
Jun 25 12:38:52 mattermost[46974]: {"timestamp":"2024-06-25 12:38:52.938 +01:00","level":"info","msg":"rtc: server is listening on udp 192.168.64.4:8443","caller":"app/plugin_api.go:1004","plugin_id":"com.mattermost.calls","origin":"main.(*logger).Info log.go:104"}
Jun 25 12:38:52 mattermost[46974]: {"timestamp":"2024-06-25 12:38:52.940 +01:00","level":"info","msg":"rtc: server is listening on udp 192.168.64.4:8443","caller":"app/plugin_api.go:1004","plugin_id":"com.mattermost.calls","origin":"main.(*logger).Info log.go:104"}
Jun 25 12:38:52 mattermost[46974]: {"timestamp":"2024-06-25 12:38:52.941 +01:00","level":"info","msg":"Listening TCP on 0.0.0.0:8443","caller":"app/plugin_api.go:1004","plugin_id":"com.mattermost.calls","origin":"main.(*logger).Info log.go:104","origin":"ice/v2.(*TCPMuxDefault).start github.com/pion/ice/v2@v2.3.11/tcp_mux.go:80"}
Jun 25 12:38:53 mattermost[46974]: {"timestamp":"2024-06-25 12:38:53.473 +01:00","level":"info","msg":"plugin process exited","caller":"plugin/hclog_adapter.go:61","plugin_id":"playbooks","wrapped_extras":"pluginplugins/playbooks/server/dist/plugin-linux-amd64id47020"}
Jun 25 12:38:53 mattermost[46974]: {"timestamp":"2024-06-25 12:38:53.473 +01:00","level":"error","msg":"Unable to activate plugin","caller":"app/plugin.go:144","plugin_id":"playbooks","bundle_path":"plugins/playbooks","error":"failed to ensure bot: failed to set profile image: SetProfileImage: Couldn't upload profile image."}
Jun 25 12:38:53 systemd[1]: Started mattermost.service - Mattermost: collaboration platform.
Jun 25 12:38:53 mattermost[46974]: {"timestamp":"2024-06-25 12:38:53.558 +01:00","level":"info","msg":"Starting Server...","caller":"app/server.go:879"}
Jun 25 12:38:53 mattermost[46974]: {"timestamp":"2024-06-25 12:38:53.558 +01:00","level":"info","msg":"Server is listening on 127.0.0.1:15212","caller":"app/server.go:955","address":"127.0.0.1:15212"}
Jun 25 12:38:53 mattermost[46974]: {"timestamp":"2024-06-25 12:38:53.558 +01:00","level":"info","msg":"Sending systemd READY notification.","caller":"commands/server.go:130"}
Jun 25 12:39:18 mattermost[46974]: {"timestamp":"2024-06-25 12:39:18.713 +01:00","level":"info","msg":"Worker: Job is complete","caller":"jobs/batch_migration_worker.go:71"}
Jun 25 12:39:18 mattermost[46974]: {"timestamp":"2024-06-25 12:39:18.713 +01:00","level":"info","msg":"Worker: Job is complete","caller":"jobs/batch_migration_worker.go:71"}
Jun 25 12:40:00 mattermost[46974]: {"timestamp":"2024-06-25 12:40:00.002 +01:00","level":"error","msg":"Failed to get system bot","caller":"app/post.go:2216","component":"post_reminders","error":"GetSystemBot: List of admins is empty."}
Jun 25 12:40:02 mattermost[46974]: {"timestamp":"2024-06-25 12:40:02.930 +01:00","level":"info","msg":"Worker: Job is complete","caller":"migrations/worker.go:129","worker_name":"Migrations","job_id":"i6rcrd9wdjg5td7absu5gqt7jw","job_type":"migrations","job_create_at":"Jun 25 11:39:50.899"}

jwqos · June 27, 2024, 10:11am

If it’s usefull somehow, I installed kernel 6.6 on a raspberry pi4 running ynh and it works smooth as before with kernel 6.1

tommi · June 28, 2024, 6:42am

I share the excitement and impatience to get YunoHost 12, but I want to reply to all the people who have been asking and pressing for a timeline: if you are so eager and so aggressive, why are you using YunoHost in the first place?

This software is about alternative, human, small, simple, calm technology, not the one with deadlines, speed, and broken things.

TBH I love when something breaks in YunoHost because I know that it’s because it’s simple and volunteer-maintained, not because it’s the choice of a big corporation to “move fast and break things!”

To YunoHost contributors: thank you, you are awesome!

jookk · July 3, 2024, 12:00pm

is it usable for mail server, nextcloud and wordpess allready?
Thanks for nice work, which you are doing .)

jgreyz · July 5, 2024, 10:22pm

Is there an Alpha or Beta process to upgrade Yunohost 11 to 12? I’m having trouble locating one, so not sure if there is one or not at this time.

tituspijean · July 6, 2024, 8:39am

In the first post of this thread, look for “migrating”.

mabap · July 14, 2024, 1:32pm

dnsrecords part of “Diagnose” function throws runtime error

After installing the latest copy of yunohost according to the top posting an a fresh debian 12.6, I get a runtime error when running Diagnosis:
— snip —

Diagnose fehlgeschlagen für die Kategorie 'dnsrecords':
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/yunohost/diagnosis.py", line 183, in diagnosis_run
code, report = diagnoser.diagnose(force=force)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/diagnosis.py", line 435, in diagnose
items = list(self.run())
^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/diagnosers/12-dnsrecords.py", line 57, in run
for report in self.check_domain(
File "/usr/lib/python3/dist-packages/yunohost/diagnosers/12-dnsrecords.py", line 121, in check_domain
if self.current_record_match_expected(r):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/diagnosers/12-dnsrecords.py", line 220, in current_record_match_expected
key, value = param.split("=")
^^^^^^^^^^
ValueError: not enough values to unpack (expected 2, got 1)

— snip —
Relevant domain is “intcloud.retsiemuab.de”
It does not have “DMARC1” entries in its TXT record (which is what the failed function seems to check) but it does have an spf1 entry (automatically added by my domain provider which is also my e-mail provider). Removing that seems to help (most probably because then there is no TXT record) but I added it again so the bug can be reproduced (once DNS updates ripple through).

Aleks · July 31, 2024, 4:19pm

(closing in favor of Beta-stage testing for YunoHost 12.0/Bookworm and Bullseye->Bookworm migration)