[09:13:34]
<kayou> > <@kayou:matrix.org> i can't do it right now, but if you want to fix the ci, you can juste the --break-the-system option here (but only for bookworm)
done
[09:31:09]
<Yunohost Git/Infra notifications> [yunohost] @kay0u pushed 1 commit to bookworm: ci: dont install any package with pip, its supposed to be preinstalled ([734db199](https://github.com/YunoHost/yunohost/commit/734db1994c30faac1d9d14ab40d32a275245f567))
[09:45:26]
<Yunohost Git/Infra notifications> 🏗️ Starting build for yunohost/12.0.0+202305160945 for bookworm/unstable/all ...
[09:46:46]
<Yunohost Git/Infra notifications> ✔️ Completed build for yunohost/12.0.0+202305160945 for bookworm/unstable/all.
[09:56:23]
<Yunohost Git/Infra notifications> [yunohost] 🔴 Pipeline [#868659943](https://gitlab.com/yunohost/yunohost/-/pipelines/868659943) failed on branch bookworm
[10:10:20]
<kayou> FYI I changed to 1 (3 previously) the number of runner for the ci core
[10:14:28]
<Yunohost Git/Infra notifications> [yunohost-ci] @kay0u pushed 1 commit to master: remove buster, add bookworm support ([c08a409f](https://github.com/YunoHost/yunohost-ci/commit/c08a409fe31f0d5de163c10886ff6da8ec1d6824))
[13:54:38]
<Yunohost Git/Infra notifications> [yunohost-ci] @kay0u pushed 1 commit to use-snapshot: use a snapshot instead of recreating a container from scratch ([77714919](https://github.com/YunoHost/yunohost-ci/commit/777149191b645211b46721d7b439177d43f5db70))
[13:54:38]
<Yunohost Git/Infra notifications> [yunohost-ci] @kay0u created new branch use-snapshot
[14:37:55]
<Yunohost Git/Infra notifications> [yunohost] 🔴 Pipeline [#868659943](https://gitlab.com/yunohost/yunohost/-/pipelines/868659943) failed on branch bookworm
[14:54:05]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin pushed 3 commits to bookworm ([734db1994c30...3b7548592304](https://github.com/YunoHost/yunohost/compare/734db1994c30...3b7548592304))
[14:54:08]
<Yunohost Git/Infra notifications> [yunohost/bookworm] tests: fix remaining funky mocker.spy - Alexandre Aubin
[14:54:11]
<Yunohost Git/Infra notifications> [yunohost/bookworm] tests: fix bad regex permission test because python3.11 now accepts ++ quantifier, so change the bad regex trick - Alexandre Aubin
[14:54:13]
<Yunohost Git/Infra notifications> [yunohost/bookworm] tests: somehow using Domain as http header aint supported anymore, gotta use Host - Alexandre Aubin
[15:00:25]
<Yunohost Git/Infra notifications> 🏗️ Starting build for yunohost/12.0.0+202305161500 for bookworm/unstable/all ...
[15:01:15]
<Yunohost Git/Infra notifications> ✔️ Completed build for yunohost/12.0.0+202305161500 for bookworm/unstable/all.
[15:27:17]
<tituspijean[m]> @Aleks and others cf. https://forum.yunohost.org/t/plus-rien-dans-application/24768/11
Since crashing Python dependencies happens oftentimes when someone plays with `sudo pip` on their server, shouldn't we have YunoHost run in its own `venv`?
[15:28:06]
<Aleks (he/him/il/lui)> 😬
[15:28:31]
<Aleks (he/him/il/lui)> maybe ...
[15:29:15]
<tituspijean[m]> #yakafokon
[15:29:49]
<Aleks (he/him/il/lui)> idk, it's a mess, i mean, yunohost is installed as a .deb and the corresponding python file go into the regular /usr/lib/python/dist-packages, it would be super funky if a dist-package in fact runs in a python venv
[15:30:18]
<Aleks (he/him/il/lui)> but we could also trick python and remove "/usr/local/bin" from the python path at the very beginning of the yunohost bin
[15:31:05]
<Aleks (he/him/il/lui)> like right after https://github.com/YunoHost/yunohost/blob/dev/bin/yunohost#L4, something like `sys.path.remove('/usr/local/python')` or idk
[15:31:30]
<Aleks (he/him/il/lui)> and at the same time i'm almost glad that people that run random script on their server get things fucked up ...
[15:31:32]
<Yunohost Git/Infra notifications> [yunohost-ci] @kay0u pushed 1 commit to use-snapshot: fix update container ([9c23d090](https://github.com/YunoHost/yunohost-ci/commit/9c23d090fb41f92b8180ff466681d3541fdcce3a))
[15:32:55]
<Aleks (he/him/il/lui)> i mean it ain't for no reason that `pip` now mandats the `--break-the-system` option when installing shit on the global scope on Python 3.11 / Bookworm
[15:34:15]
<tituspijean[m]> ah nice, I thought it came from us when I saw you referring to it with kay0u
[15:34:18]
<Aleks (he/him/il/lui)> `pip install foobar` be like https://www.youtube.com/watch?v=xroDBOK88sQ
[15:36:55]
<Aleks (he/him/il/lui)> so idk i'm torned between "Let's tweak python's path to avoid loading /usr/local/python" and "If we automagically avoid loading /usr/local/python, it almost encourage people to run *even more* random scripts from the internets" >_> ...
[15:39:29]
<tituspijean[m]> ¯\_(ツ)_/¯
[15:40:05]
<tituspijean[m]> It would push the "beyond recoverable failure" threshold a bit further 😛
[15:55:01]
<kayou> Aleks (he/him/il/lui): do you understand why we don't have dns working on bookworm (on the ci at least?)
[15:55:13]
<kayou> ```
lxc exec "$1" -- /bin/bash -c "echo 'resolv-file=/etc/resolv.dnsmasq.conf' > /etc/dnsmasq.d/resolvconf"
lxc exec "$1" -- /bin/bash -c "echo 'nameserver 8.8.8.8' > /etc/resolv.dnsmasq.conf"
lxc exec "$1" -- /bin/bash -c "sed -i 's/#IGNORE/IGNORE/g' /etc/default/dnsmasq"
lxc exec "$1" -- /bin/bash -c "systemctl restart dnsmasq"
lxc exec "$1" -- /bin/bash -c "journalctl -u dnsmasq -n 100 --no-pager"
```
[15:55:25]
<Aleks (he/him/il/lui)> hmmyeah that's some ugly fix
[15:55:55]
<Aleks (he/him/il/lui)> i'm not 100% sure what the source of the issue is
[15:55:58]
<kayou> is it a bug to fix?
[15:56:07]
<kayou> or just an issue with the ci?
[15:56:18]
<Aleks (he/him/il/lui)> something to do with /etc/resolv.conf pointing to 127.0.0.1 before yunohost install is done
[15:56:35]
<Aleks (he/him/il/lui)> and dnsmasq has like no actual resolver to work with
[15:57:09]
<Aleks (he/him/il/lui)> so i brute-forced it with the lines adding 8.8.8.8 in `/etc/resolv.dnsmasq.conf` (arbitrary-chosen filename)
[15:57:38]
<Aleks (he/him/il/lui)> and for some reason i also had to uncomment the "IGNORE" line thingy, don't remember why
[15:57:53]
<Aleks (he/him/il/lui)> but the real question is why was it working without this fix in bullseye
[15:58:30]
<Aleks (he/him/il/lui)> and also yeah, curious to know what happen on vanilla debian after `apt install resolvconf dnsmasq` (without yunohost)
[16:12:06]
<Yunohost Git/Infra notifications> [yunohost-ci] @kay0u pushed 1 commit to use-snapshot: fix prepare script ([e96a3cb5](https://github.com/YunoHost/yunohost-ci/commit/e96a3cb52802b57fde3b63b1d0f3c6e332974004))
[16:44:24]
<kayou> hmmm
[16:45:13]
<kayou> I have increased some kernel values on Harissa
[16:45:41]
<kayou> ```
fs.inotify.max\_queued\_events
fs.inotify.max\_user\_instances
fs.inotify.max\_user\_watches
```
[16:45:52]
<kayou> ```
fs.inotify.max_queued_events
fs.inotify.max_user_instances
fs.inotify.max_user_watches
```
[16:46:51]
<kayou> we had reached the limit
[16:54:19]
<kayou> FYI, there is a new container on harissa (because IDK why but i couldn't add a btrfs volume on ci-gitlab-core)
3 runners are running, using btrfs, and snapshot instead of using dir volume, and create new container on each test
[16:54:19]
<kayou> https://gitlab.com/kay0u/yunohost/-/pipelines/869211528
[16:54:53]
<kayou> if it works, i'll probably use this new method
[17:53:52]
<Yunohost Git/Infra notifications> [yunohost] 🔴 Pipeline [#869081173](https://gitlab.com/yunohost/yunohost/-/pipelines/869081173) failed on branch bookworm
[17:56:13]
<Aleks (he/him/il/lui)> >/opt/yunohost-ci/run.sh: line 39: 3651891 Killed lxc exec "$CONTAINER_ID" /bin/bash < "${1}"
137
in https://gitlab.com/yunohost/yunohost/-/jobs/4294689037 😬
[17:56:26]
<Aleks (he/him/il/lui)> but still more reliable apparently, assuming nobody restarted the jobs or anything
[18:16:17]
<Yunohost Git/Infra notifications> Failed to run the source auto-update for : dokuwiki, zwave-js-ui. Please run manually the autoupdate_app_sources.py script on these apps to debug what is happening!
[20:09:13]
<Yunohost Git/Infra notifications> @aya forked yunohost to [aya/yunohost](https://github.com/aya/yunohost)
[20:36:23]
<Yunohost Git/Infra notifications> [yunohost] @aya opened [pull request #1661](https://github.com/YunoHost/yunohost/pull/1661): keep fail2ban rules on firewall reload