[06:56:44]
<Yunohost Git/Infra notifications> [issues] Beeblebrox-BSD opened [issue #2577](https://github.com/YunoHost/issues/issues/2577): Yunohost/Trixie repo problem
[07:05:54]
<Yunohost Git/Infra notifications> [issues] ericgaspar [commented](https://github.com/YunoHost/issues/issues/2577#issuecomment-2814724862) on [issue #2577](https://github.com/YunoHost/issues/issues/2577) Yunohost/Trixie repo problem: YunoHost is not yet compatible with Trixie.
[07:08:54]
<Yunohost Git/Infra notifications> [issues] Beeblebrox-BSD opened [issue #2578](https://github.com/YunoHost/issues/issues/2578): LLM API through Yunohost Base for Apps Access
[07:10:41]
<Yunohost Git/Infra notifications> [issues] Beeblebrox-BSD closed [issue #2577](https://github.com/YunoHost/issues/issues/2577): Yunohost/Trixie repo problem
[07:10:42]
<Yunohost Git/Infra notifications> [issues] Beeblebrox-BSD [commented](https://github.com/YunoHost/issues/issues/2577#issuecomment-2814735277) on [issue #2577](https://github.com/YunoHost/issues/issues/2577) Yunohost/Trixie repo problem: OK, thanks.
The Trixie install script implied some level of compatibility and caused confusion.
[08:59:20]
<Yunohost Git/Infra notifications> [yunorunner] Salamandar merged [pull request #72](https://github.com/YunoHost/yunorunner/pull/72): Bump jinja2 from 3.1.4 to 3.1.6
[08:59:21]
<Yunohost Git/Infra notifications> [yunorunner] Salamandar pushed 1 commit to main: Bump jinja2 from 3.1.4 to 3.1.6 Bumps [jinja2](https://github.com/pallets/jinja) from 3.1.4 to 3.1.6. - [Release notes]... ([39f89917](https://github.com/YunoHost/yunorunner/commit/39f899170fcd3978a84555d6abea91e3997f18f7))
[08:59:23]
<Yunohost Git/Infra notifications> [yunorunner] Salamandar deleted branch dependabot/pip/jinja2-3.1.6
[09:00:06]
<Yunohost Git/Infra notifications> [yunorunner] Salamandar closed [issue #32](https://github.com/YunoHost/yunorunner/issues/32): End time isnt cleared on a running job
[09:00:07]
<Yunohost Git/Infra notifications> [yunorunner] Salamandar [commented](https://github.com/YunoHost/yunorunner/issues/32#issuecomment-2814962664) on [issue #32](https://github.com/YunoHost/yunorunner/issues/32) End time isnt cleared on a running job: Should be fixed now ?
[11:38:39]
<lautre> I'm installing Yunohost on a fresh **minimalist** container.
First fail : ping failled... need install inet-utils packages
May be this case (no ping command) should be detected ?
[11:39:34]
<Salamandar> what is the minimalist container ?
[11:44:22]
<lautre> Not like almaslinux, but with very few packages installed from debootstrap
[11:44:26]
<lautre> Of course, I added vim for confort
[11:46:23]
<lautre> The installation failled.
I not yet read the log, I'm trying the command :
`apt install --assume-yes -o Dpkg::Options::=--force-confold -o APT::install-recommends=true yunohost yunohost-admin postfix`
Just to see if it's same like apt-get
[11:47:20]
<lautre> Oki, it's failed because networks or apt-cache problem. (Like, it's can be my fault)
[11:51:16]
<lautre> Seems works fine without apt-cacher-ng in the /etc/apt/apt.conf (It's from my default setting)
[13:00:07]
<Yunohost Git/Infra notifications> Salamandar edited repository test_apps: Dummy apps designed for unit tests of Yunohost https://github.com/YunoHost/test_apps
[13:00:07]
<Yunohost Git/Infra notifications> [test_apps] Salamandar deleted branch master
[13:00:08]
<Yunohost Git/Infra notifications> [test_apps] Salamandar created new branch main
[13:00:38]
<Yunohost Git/Infra notifications> [vinaigrette] Salamandar created new branch main
[13:00:42]
<Yunohost Git/Infra notifications> Salamandar edited repository vinaigrette: Build those damn .debs https://github.com/YunoHost/vinaigrette
[13:00:43]
<Yunohost Git/Infra notifications> [vinaigrette] Salamandar deleted branch master
[13:02:11]
<Yunohost Git/Infra notifications> [infra] Salamandar deleted branch master
[13:02:11]
<Yunohost Git/Infra notifications> Salamandar edited repository infra https://github.com/YunoHost/infra
[13:02:11]
<Yunohost Git/Infra notifications> [infra] Salamandar created new branch main
[14:50:21]
<Salamandar> @Alekswag:matrix.org I would love if all the python "resources" (go, apt, etc) that are basically duplicates from bash helpers were split in a sub-library that could be called like `bash -c python 'import yunohost.helpers; …'` without loading the whole yunohost stuff. That would prevent code duplication.
[14:55:09]
<Aleks (he/him/il/lui)> Yeah it's in my mental todolist to have something like this
[14:55:52]
<Aleks (he/him/il/lui)> At least was planning for something like this for packaging v3 for the configuration/templating mechanism
[14:56:52]
<Salamandar> ah okay, cool :)
[15:03:40]
<Aleks (he/him/il/lui)> (I mean I hope to eradicate as much of the helper as we can for the 'v3 helpers' (maybe backports some idea for v2.1 idk), ideally down to 5~3 file but I still need to sit down and look/think about it in details
[15:07:17]
<Salamandar> ```
░▒▓█ for brow in $(gh repo list "YunoHost" --json "name,defaultBranchRef" --jq '.[] | @base64'); do
row=$(echo "$brow" | base64 -d) ; name=$(echo "$row" | jq -r '.name') ; branch=$(echo "$row" | jq -r '.defaultBranchRef.name')
if [[ "$branch" == "master" ]]; then echo "$name: $branch"; fi
done
apps: master
doc: master
doc.yunohost.org: master
```
[15:07:22]
<Salamandar> doc will be "migrated" to main with docusaurus
[15:07:29]
<Salamandar> and apps… brrr that will be a nightmare to rename
[15:10:09]
<Salamandar> the next infra change I would like to do would be to split the "repo.yunohost.org" host from the machine actually doing the builds
[15:10:36]
<Salamandar> one would just serve static files, the other would make some computing / io
[15:14:55]
<Salamandar> (although reprepo would still run on the files server i guess)
[20:29:24]
<rodinux> Hello, I am affraid about this discuss https://forum.yunohost.org/t/fresh-install-12-0-14-pas-de-mail-root-et-groupe-admins-non-peuple/36529/13
Does this bug is knowned for us ?
[22:10:43]
<Aleks (he/him/il/lui)> hmpf i checked my setup which i redid like last week and indeed there's no alias configured on the admins group ~_~
[22:11:49]
<rodinux> Ok so it's normal... Jarod5001 was explaining that also...
[22:12:28]
<Aleks (he/him/il/lui)> well it's a bug tho 😬
[22:16:16]
<rodinux> As you like said «All Machines are Brokens...»
[22:18:14]
<Aleks (he/him/il/lui)> hmf so that's because of https://github.com/YunoHost/yunohost/commit/27611864d2aa1c126598a5c43036d25b1fc907a7#diff-24c783c1e108af4846094b6b66f6be63c3304e9f92e61cb9b20f99db409d4738
[22:18:14]
<Aleks (he/him/il/lui)> the call to `_update_admins_group_aliases` was moved inside the `if os.path.exists("/etc/yunohost/installed")`
[22:18:31]
<Aleks (he/him/il/lui)> not sure how that's related to the intention of fixing offline installs
[22:19:31]
<rodinux> what's offline installs ? only for local ?
[22:21:17]
<Aleks (he/him/il/lui)> like with no internet connectivity
[22:23:52]
<rodinux> but the file /etc/yunohost/installed should exist... so why ?
[22:25:00]
<rodinux> ah sorry I inverse the diff...
[22:38:15]
<rodinux> There is always this code https://github.com/YunoHost/yunohost/blob/1bdff63749ba4cba010a2142e455eab14e45d11b/src/user.py#L1625-L1639