[10:23:37]
<Lukas> Hi all
[10:44:11]
<Lukas> Can't install Kresus App, here the log: https://paste.yunohost.org/raw/iziwejujib
[10:44:12]
<Lukas> I have just Element und OpenCloud installed on my YunoHost
[10:46:00]
<nicofrand> Lukas: You are using yunhost 13?
[11:04:07]
<tituspijean> The automated tests are indeed failing for this app on YunoHost 13: https://ci-apps-trixie.yunohost.org/ci/job/9475
[11:06:52]
<nicofrand> I just merged into testing a modification from alex to improve Trixie support in the kresus package
[11:10:18]
<tituspijean> @c1xx:matrix.org can you try installing the app with `yunohost app install https://github.com/YunoHost-Apps/kresus_ynh/tree/testing -f` ?
[11:10:56]
<tituspijean> (though we are basically changing the JOSE lib with that fix, hopefully they behave identically)
[11:12:58]
<Lukas> yes
[11:14:57]
<Lukas> sure, wait
[11:17:58]
<Lukas> Info: Installing kresus…
Warning: App depends on Yarn via APT, but this is not supported anymore.
Warning: Operation will most likely fail. You need to manually install Yarn before retrying.
Warning: Continuing, but this will become a hard error in the future...
Info: Provisioning sources...
Info: Provisioning system_user...
Info: Provisioning install_dir...
Info: Provisioning data_dir...
Info: Provisioning permissions...
Info: Provisioning ports...
Info: Provisioning apt...
Warning: /var/cache/debconf/tmp.ci/postgresql.config.iuPnz3: 12: pg_lsclusters: not found
Info: Provisioning database...
Info: Provisioning nodejs...
Info: [++..................] > Setting up source files...
Info: [##+++...............] > Configuring NGINX web server...
Info: [#####+++............] > Installing woob...
Info: [########+++.........] > Installing kresus...
Error: Unable to install kresus: An error occurred inside the app installation script
Info: The operation 'Install the '{}' app' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20251201-111517-app_install-kresus' to get help
Warning: Here's an extract of the logs before the crash. It might help debugging the error:
Info: DEBUG - zeep 4.3.1 requires isodate>=0.5.4, but you have isodate 0.0.0 which is incompatible.
Info: DEBUG - softlayer 6.2.5 requires rich==13.7.1, but you have rich 13.9.4 which is incompatible.
Info: DEBUG - wheel 0.46.1 requires packaging>=24.0, but you have packaging 23.2 which is incompatible.
Info: DEBUG - Successfully installed Babel-2.17.0 BeautifulSoup4-4.14.3 Pillow-12.0.0 PyExecJS-1.5.1 PyYAML-6.0.3 certifi-2025.11.12 cffi-2.0.0 charset-normalizer-3.4.4 chompjs-1.4.0 cryptography-46.0.3 html2text-2025.4.15 idna-3.11 lxml-6.0.2 markdown-it-py-4.0.0 mdurl-0.1.2 packaging-23.2 pdfminer.six-20251107 pycountry-24.6.1 pycparser-2.23 pygments-2.19.2 python-dateutil-2.9.0.post0 requests-2.32.5 rich-13.9.4 simplejson-3.20.2 six-1.17.0 soupsieve-2.8 termcolor-3.2.0 typing-extensions-4.15.0 unidecode-1.4.0 urllib3-2.5.0 woob-3.7
Info: DEBUG - + ynh_safe_rm /var/www/kresus/.cargo
Info: DEBUG - + local target=/var/www/kresus/.cargo
Info: DEBUG - + ynh_safe_rm /var/www/kresus/.rustup
Info: DEBUG - + local target=/var/www/kresus/.rustup
Info: DEBUG - + ynh_safe_rm /var/www/kresus/.cache
Info: DEBUG - + local target=/var/www/kresus/.cache
Info: DEBUG - + ynh_safe_rm /var/www/kresus/.local
Info: DEBUG - + local target=/var/www/kresus/.local
Info: INFO - [########+++.........] > Installing kresus...
Info: DEBUG - + pushd /var/www/kresus
Info: DEBUG - /var/www/kresus /var/cache/yunohost/app_tmp_work_dirs/app_pco0298z/scripts
Info: DEBUG - + ynh_hide_warnings ynh_exec_as_app yarn config set network-timeout 300000
Info: DEBUG - + ynh_exec_as_app yarn config set network-timeout 300000
Info: DEBUG - + sudo -u kresus env PATH=/opt/node_n/n/versions/node/20.19.6/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin COREPACK_ENABLE_DOWNLOAD_PROMPT=0 NPM_CONFIG_UPDATE_NOTIFIER=false yarn config set network-timeout 300000
Info: DEBUG - env: ‘yarn’: No such file or directory
Info: DEBUG - + ynh_exit_properly
Warning: Removing the app after installation failure…
Info: [++++++++++..........] > Removing system configurations related to kresus...
Info: [####################] > Removal of kresus completed
Warning: App depends on Yarn via APT, but this is not supported anymore.
Warning: Operation will most likely fail. You need to manually install Yarn before retrying.
Warning: Continuing, but this will become a hard error in the future...
Info: Deprovisioning nodejs...
Info: Deprovisioning database...
Info: Deprovisioning apt...
Info: Deprovisioning ports...
Info: Deprovisioning permissions...
Info: Deprovisioning data_dir...
Info: Deprovisioning install_dir...
Info: Deprovisioning system_user...
Info: Deprovisioning sources...
Error: The operation 'Install the '{}' app' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20251201-111517-app_install-kresus' to get help
[11:38:11]
<nicofrand> https://wiki.debian.org/Yarn might need changes
[11:38:52]
<nicofrand> unless https://github.com/YunoHost-Apps/kresus_ynh/blob/master/manifest.toml#L67C23-L67C53 is enough
[11:43:07]
<Salamandar> No, yarn is not installed from deb anymore
[11:43:08]
<Salamandar> and should not
[11:43:34]
<Salamandar> > Warning: App depends on Yarn via APT, but this is not supported anymore.
[11:45:13]
<nicofrand> yes, but what's the purpose of `extras.yarn.repo` then
[11:45:54]
<Salamandar> it's legacy
[11:45:59]
<Salamandar> for debian 12
[11:46:17]
<Salamandar> kresus is indeed broken on debian 13
[11:47:41]
<Salamandar> you need to run something like corepack enable iirc
[11:48:16]
<Salamandar> I also see `corepack prepare yarn@latest --activate`
[11:51:19]
<orhtej2> > <@Salamandar:matrix.org> I also see `corepack prepare yarn@latest --activate`
There's a difference between yarn from extras 1.x vs the one from corepack 4.x
[11:51:32]
<orhtej2> make sure it's the one you want
[11:56:04]
<Salamandar> Yes installing from deb is deprecated for a long time
[12:05:09]
<orhtej2> Sure, what's the official way of getting yarn 1.x
[12:06:29]
<orhtej2> https://classic.yarnpkg.com/en/docs/install#debian-stable npm to the rescue I guess
[12:12:47]
<Salamandar> I'm not sure there is any reason to want 1.x
[12:50:20]
<nicofrand> Yarn 2+ is completely different afair, lock files etc would not match afair
[12:50:38]
<nicofrand> that would require proper tests from the software pov
[12:52:29]
<nicofrand> I'd rather go back to npm 🤷♂️
[12:59:51]
<Aleks (he/him/il/lui)> https://aria.im/_bifrost/v1/media/download/ASrD9q_AGbC6zAhT_FSAw20IpLxt8_CA9gHvHvjHzyfP4Hv5GzyDs89bb1ZNyEpksv5rpi_XpXKDv0ZYS8Z5MNlCea3yXaEAAG1hdHJpeC5vcmcvZ0twcVBTZWlUc1hZYWNuRU5LRXlBb1NN
[13:00:46]
<nicofrand> https://doc.yunohost.org/fr/dev/packaging/resources#example l'example aura le même souci
[13:13:10]
<Lukas> so an app issue in YNH 13 ?
[13:27:03]
<nicofrand> yes
[13:30:28]
<Lukas> ok then I wait for fixes :)
[15:43:46]
<trendless> seems like opencloud 4.0 upgrade might've broken login again.
[16:01:02]
<lautre> Sur la doc, https://doc.yunohost.org/fr/admin/command_line
Est ce qu'il y a quelque part l'ensemble de l'arborescence des paramètres pour la commande yunohost?
[16:04:54]
<Aleks (he/him/il/lui)> non, à part dans https://github.com/YunoHost/yunohost/blob/dev/share/actionsmap.yml mais c'est un peu "du code"
[16:05:55]
<Aleks (he/him/il/lui)> j'ai vaguement une idée en tête que faudrait faire une doc auto-générée à partir de ça, un peu comme on a pour les helpers avec https://yunohost.org/packaging_apps_helpers_v2.1 mais ENOTIME et théoriquement la priorité du projet devrait être la webadmin et pas la CLI, mais bon, ce serait nice-to-have quand même
[16:07:05]
<isAAAc> yunohost -h c'est pas complet ?
[16:07:47]
<Aleks (he/him/il/lui)> bah tu dois descendre dans chacunes des categories, action etc et faire --help à chaque fois quoi
[16:08:12]
<Aleks (he/him/il/lui)> du coup quand tu veux explorer et avoir la vue d'ensemble c'est pas pratique de devoir lancer 150 --help différent
[16:08:23]
<isAAAc> oui j'avoue
[16:12:26]
<Salamandar> hmmmm
[16:21:54]
<Salamandar> With some custom code :
[16:21:56]
<Salamandar> https://aria.im/_bifrost/v1/media/download/ARio8jcsGlMFJKUlMy40F_4TlrhrvngLQZpjIVK_JLqg45WHCIydUH_tqSwxJqIuOyZWRpbr-Obss0YVD1IIOG1Cea397f5gAG1hdHJpeC5vcmcvS29SeXlyak9WdFJCc2VxbkphZGJWSXVl
[16:33:30]
<Salamandar> but i'm not sure about how *not* make this very, very, very verbose…
[16:42:26]
<lautre> J'ai ma VM sur la table d'opération. Je voulais voir si je pouvais faire une sauvegarde de chaque application.
J'ai fini par voir que c'était yunohost backup --app truc
Mais oui, avoir une vue globale, ce serait pas mal.
Faudrait arriver à le générer automatiquement en schéma, et que ce soit aussi dans le --help tant qu'à faire.
oui, encore du travail, et je ne saurai pas le faire. Quoique... faudrait un dev, un vrai
[16:43:02]
<lautre> Ma VM est cassée, mais ce n'est pas la faute de Yunohost, c'est juste moi qui ai déconné, il y a quelques mois
[17:03:19]
<Salamandar> en schéma ?
[17:04:07]
<lautre> Je ne sais plus comment ça s'appelle, quelque chose comme Mermaid pour générer un graphique
[17:05:57]
<lautre> Mais en fait, l'idéal serait que ça s'affiche bien en ncurse/cli
[17:09:17]
<lautre> Si je fais quelque chose, ce serait de sortir les "help", de repérer les lignes avec {...} et de générer ce qu'il faut, mais je vais galérer, ça risque d'être lourd à débuguer et heu, il y a forcément plus simple
[17:09:38]
<Chatpitaine Caverne> lautre: Tu peux même sauvegarder les parties système séparément :
`yunohost backup create --name NOM_DU_BACKUP --description "DESCRIPTION" --methods tar --system SYSTEM`
ou SYSTEM peut prendre les valeurs :
- conf\_ynh\_settings
- conf\_manually\_modified\_files
- conf\_ynh\_certs
- data\_xmpp
- data\_home
- data\_mail
- data\_multimedia
- conf\_ldap
C'est dans l'ordre de sauvegarde complet par Yunohost et dans l'ordre de restauration.
ça m'a été utile une fois où j'avais vraiment déconné.
[17:09:47]
<lautre> Concernant les backups, j'ai la partie base de données qui est HS.
[17:11:33]
<lautre> Alors oui, j'ai bien les fichiers bruts des DB, probablement dans /var/mysql mais bon, je répare tranquillement la VM.
J'ai monté le système de fichiers et fait un chroot. C'est très lent pour chaque changement de paquet dans aptitude, mais dans quelques heures ça devrait le faire (toujours le problème avec les paquets cassés, ça prend du temps, et on n'est jamais certain d'arriver jusqu'au bout)
[17:12:29]
<lautre> Je note l'info sur les valeurs que peut prendre SYSTEM
[19:01:47]
<azib> Hello Salamandar, I sent you a test message via Matrix (sorry, I found the contact in some thread where you suggested pinging to). Can you confirm that you have received it?
[19:02:13]
<azib> Hi, folks
[19:07:20]
<azib> I'm new to the YunoHost approach, I really appreciate being able to have many well-integrated apps in a simple way, but I'm fond of my old Podman/Traefik... So I thought of creating a container with Incus where I could make my playground.I was wondering if with Traefik or not I can elegantly display my podman containers behind Nginx
[19:11:53]
<Aleks (he/him/il/lui)> don't know about the "display podman containers" part, but as for exposing containers (or LXC) to the internets, you'll probably want to use `redirect_ynh` which can be used to configure a reverse proxy and the "portal tile" / yunohost ACL (the app is badly named imho, or rather should be split into a `redirect_ynh` and `reverseproxy_ynh` or even integrated directly into YunoHost's core)
[19:22:47]
<azib> `redirect_ynh` is a command or you refer to the app https://apps.yunohost.org/app/redirect ?
edit: https://github.com/YunoHost-Apps/redirect_ynh ok, thanks
[19:23:24]
<Aleks (he/him/il/lui)> the `redirect_ynh` app
[19:24:00]
<Aleks (he/him/il/lui)> maybe there's a portainer something web dashboard that would be compatible with podman to manage containers idk
[19:32:40]
<azib> there is no problem, podman on cli is beautiful, i can interact with it from ssh...
I prefer work directly in code-server terminal, but from here i have no privileged permission, so can't do:
~$ sudo incus exec podman-container /bin/sh
sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
[19:33:16]
<azib> there is no problem, podman on cli is beautiful, i can interact with it from ssh...
I prefer work directly in code-server terminal, but from here i have no privileged permission, so can't do:
~$ sudo incus exec podman-container /bin/sh
sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
```
[19:33:47]
<azib> there is no problem, podman on cli is beautiful, i can interact with it from ssh...
I prefer work directly in code-server terminal, but from here i have no privileged permission, so can't do:
```
~$ sudo incus exec podman-container /bin/sh
sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
```
[19:34:38]
<azib> there is no problem, podman on cli is beautiful, i can interact with it from ssh...
I prefer work directly in code-server terminal, but from here i have no privileged permission, so can't do:
```
~$ sudo incus exec podman-container /bin/sh
sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
```
(code-server is a normal yunohost app installation)
[19:40:11]
<azib> Sorry for the confusion with the last few messages....
I can still access the shell from Cockpit.
[19:40:55]
<azib> (with privileges)
[21:45:35]
<lautre> If I remove the Yunohost package from the system, will the databases will be removed too? (and other files too ?)
[21:55:30]
<lautre> I think I will make a copy of the VM before trying this. Tomorrow :D
[21:55:40]
<lautre> Good night
[21:55:50]
<orhtej2> if you don't `apt autoremove` then probably not
[21:56:33]
<lautre> I won't do "purge". I note about "autoremove"
[21:56:58]
<lautre> Will tel you tomorrow, after the copy. Safer
[21:57:00]
<lautre> :D
[21:57:13]
<lautre> Thanks