[18:16:55]
<Yunohost Git/Infra notifications> Failed to run the source auto-update for : dokuwiki, shiori, zwave-js-ui. Please run manually the autoupdate_app_sources.py script on these apps to debug what is happening!
[20:28:42]
<Yunohost Git/Infra notifications> [yunohost] @Salamandar opened [pull request #1670](https://github.com/YunoHost/yunohost/pull/1670): Allow passing a list in the manifest.toml for the apt resource packages
[20:29:48]
<Yunohost Git/Infra notifications> [yunohost] @Salamandar edited [pull request #1670](https://github.com/YunoHost/yunohost/pull/1670): Allow passing a list in the manifest.toml for the apt resource packages
[22:01:39]
<Aleks (he/him/il/lui)> meh following https://forum.yunohost.org/t/yunohost-is-a-bleeding-mess-of-file-permissions-and-locations/25075 i'm trying to figure out something to improve the SFTP situation where you basically can't do shit in /var/www/$app because only the user's app has read/write permission (and www-data typically has read permission)
[22:01:39]
<Aleks (he/him/il/lui)> or we could engineer some way to generically enable SFTP-login as $app (instead of the user identity) but not super convenient idk
[22:01:40]
<Yunohost Git/Infra notifications> [yunohost/bookworm] Merge pull request #1668 from YunoHost/enh-verbose-user_group_update more verbose logs for user_group _update - Alexandre Aubin
[22:01:40]
<Yunohost Git/Infra notifications> [yunohost] @Tagadda pushed 25 commits to bookworm ([78cd79ec480c...5a2570a5d641](https://github.com/YunoHost/yunohost/compare/78cd79ec480c...5a2570a5d641))
[22:01:40]
<Yunohost Git/Infra notifications> [yunohost/bookworm] nginx: use /var/www/.well-known folder for ynh diagnosis and acme challenge, because /tmp/ could be manipulated by user ... - Alexandre Aubin
[22:01:40]
<Yunohost Git/Infra notifications> [yunohost/bookworm] Merge branch dev into bookworm - Tagada
[22:01:40]
<Aleks (he/him/il/lui)> oooor we could add some recursive ACL for `admins` on all app folders but it's not clear when we would do this exactly ... or maybe some sort of `yunohost app add-admins-permission $app` idk
[22:01:40]
<Aleks (he/him/il/lui)> anybody has experience with tweaking stuff via SFTP ?
[22:02:50]
<Yunohost Git/Infra notifications> [yunohost] 🔴 Pipeline [#896044704](https://gitlab.com/yunohost/yunohost/-/pipelines/896044704) failed on branch bookworm
[22:03:46]
<Tag> > <@Alekswag:matrix.org> anybody has experience with tweaking stuff via SFTP ?
I use SSH and vim 🤐
I guess ACL is the way to go ? 🤔
[22:05:06]
<Aleks (he/him/il/lui)> > <@yunohostinfra:matrix.org> [yunohost] 🔴 Pipeline [#896044704](https://gitlab.com/yunohost/yunohost/-/pipelines/896044704) failed on branch bookworm
zbleuarg the CI is completely broken 😬
[22:05:36]
<Tag> Should I run the rebuild_all.sh thing as suggested ?
[22:05:38]
<Aleks (he/him/il/lui)> manually running `lxc list` I also get:
```
missing profile snap-update-ns.lxd.
Please make sure that the snapd.apparmor service is enabled and started
snap-update-ns failed with code 1
```
[22:05:38]
<Tag> ah
[22:06:30]
<Aleks (he/him/il/lui)> apparently there was some work on reworking the LXC setup, I see there's an `ci-core-gitlab2` that replaces `ci-core`
[22:07:04]
<Aleks (he/him/il/lui)> `systemctl status snapd.apparmor` shows the service as `active (exited)` with no obvious error message x_x
[22:07:11]
<Aleks (he/him/il/lui)> ah, `snap.lxd.activate` is red
[22:07:48]
<Tag> grml lets use lxd_ynh instead ? :D
[22:07:49]
<Aleks (he/him/il/lui)> ... because of the error message about "Please make sure the snapd.apparmor service is enabled" 😬
[22:08:11]
<Aleks (he/him/il/lui)> :D
[22:08:22]
<Aleks (he/him/il/lui)> or maybe just fallback to the old LXC until ka you is available to have a look
[22:15:21]
<Yunohost Git/Infra notifications> 🏗️ Starting build for yunohost/12.0.0+202306102215 for bookworm/unstable/all ...
[22:16:22]
<Yunohost Git/Infra notifications> ✔️ Completed build for yunohost/12.0.0+202306102215 for bookworm/unstable/all.
[22:20:47]
<Tag> 🚀
[22:21:33]
<Aleks (he/him/il/lui)> hmmm i'm not sure how to fix all the piping for the runner
[22:22:21]
<Tag> what do you mean ?
[22:22:58]
<Aleks (he/him/il/lui)> i dont know how gitlab and the custom runner connect each other, there doesnt seem to be any nginx endpoint 😅
[22:23:02]
<Aleks (he/him/il/lui)> sounds like it's the runner connecting to gitlab
[22:24:38]
<Tag> ah mmh I have no idea about that
[22:27:22]
<Aleks (he/him/il/lui)> ah i finally restart ci-core-gitlab2 and somehow the lxd issue disappeared ?
[22:27:33]
<Aleks (he/him/il/lui)> ihavenoideawhatimdoing.jpg
[22:27:35]
<Yunohost Git/Infra notifications> [yunohost] 🔴 Pipeline [#896044704](https://gitlab.com/yunohost/yunohost/-/pipelines/896044704) failed on branch bookworm
[22:28:24]
<Aleks (he/him/il/lui)> https://gitlab.com/yunohost/yunohost/-/jobs/4451282764 🥳
[22:28:32]
<Aleks (he/him/il/lui)> iseethisasanabsolutewin.jpg
[22:39:17]
<Tag> 🎺 victory fanfare 🎶
[22:39:39]
<Aleks (he/him/il/lui)> ff7 ? :D
[22:39:42]
<Tag> yep :D
[22:42:44]
<Tag> or is it ff7.2 vol 3 ? :o
[22:42:57]
<Tag> semver for final fantasy when?
[22:43:09]
<Aleks (he/him/il/lui)> xD
[23:15:38]
<Tag> > <@Alekswag:matrix.org> oooor we could add some recursive ACL for `admins` on all app folders but it's not clear when we would do this exactly ... or maybe some sort of `yunohost app add-admins-permission $app` idk
with packaging v2, ACL could be done while provisioning install_dir etc.. ?