[09:15:46]
<@homelab-fr:matrix.org> Un très bon article pour en savoir + sur YunoHost : https://www.clubic.com/dossier-611962-interview-yunohost.html
[09:16:11]
<@homelab-fr:matrix.org> en + j'ai compris beaucoup mieux le positionnement par rapport à l'utilisation ou pas de docker
[09:17:45]
<@homelab-fr:matrix.org> et par rapport à : "Mais, nous ne sommes pas des sectaires anti-Docker, et il serait très intéressant de voir ce que pourrait donner une distribution d'auto-hébergement basée sur Docker (ou NixOS)" je crois qu' https://umbrel.com/ est basé sur docker (mais à vérifier)
[10:00:11]
<@homelab-fr:matrix.org> Sinon je viens de voir que la roadmap est à jour : https://yunohost.org/roadmap.fr.html qu'est-ce qu'il y aura dans la version 12.2 svp ? Et savez-vous quand sortira la version 13 (pas la bêta) svp ? Merci d'avance
[10:26:18]
<Massinissa> Hello. Is this chan in French or English ?
[10:31:56]
<florent> You may speak both, yes
[10:32:27]
<florent> Avoid speaking both languages dans la même phrase otherwise we are perdu 😜
[10:32:46]
<Massinissa> ahah pas de soucis :þ
[10:36:03]
<tituspijean> La roadmap est à jour, donc la 12.2 est bien décrite pour l'instant (principalement une MAJ technique pour préparer la future migration vers la 13).
Quant à la date de sortie, comme toujours, on tourne au café et à la motivation, donc c'est quand on peut. :)
Il y a encore quelques *issues* liés à Trixie spécifiquement, donc tant qu'ils sont encore listés sur github, il est peu probable qu'on sorte la version stable.
[10:37:02]
<Massinissa> Je voulais dans un premier temps signaler un lien mort quand j'ai le message d'erreur quand je fais la mise à jour de Peertube. le lien pour le chat est https://chat.yunohost.org/ mais firefox me dit qu'il est introuvable. Je voulais faire un bug report dans le forum, mais je ne sais pas dans quelle partie du forum faire le bug report
[10:38:08]
<Massinissa> (je suis nouveau dans tout ces processus, je me disais que la partie "Support" conviendrait peut-etre, mais je voulais pas polluer le forum >< )
[10:48:05]
<tituspijean> Merci pour le signalement ! Par contre je n'arrive pas à comprendre où ce lien est affiché. Peux-tu préciser ?
[10:48:56]
<tituspijean> Ah, c'est dans la webadmin, j'ai trouvé. Merci.
[11:01:41]
<tituspijean> @_bifrost_Massinissa=2fsupport=40conference.yunohost.org:aria-net.org c'est corrigé! D'ici quelques heures https://chat.yunohost.org devrait rediriger vers https://doc.yunohost.org/community/chat_rooms/
[11:02:48]
<Massinissa> tituspijean, désolé pour l'imprécision, je comptais faire un rapport pour mon bug de MàJ peertube le précisant.
[11:11:29]
<@homelab-fr:matrix.org> Merci pour l'info !
[11:26:45]
<Massinissa> Hum, j'ai un soucis pour le bugreport de la mise à jour peertube. les logs ne mentionnent pas l'échec de la mise à jour. Le texte de la "fenetre" du message d'erreur sera suffisant ?
[16:07:14]
<Lasse Gismo> Hi there. Today my nextcloud update failed with the following logs (https://paste.yunohost.org/raw/wegihidipu). Some warnings showed me issues with dependencies and a "apt-get update --fix-missing" showed me some issues with signatures (The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 62D54FD4003F6525).
[16:07:30]
<Lasse Gismo> Any idea what do do?
[16:11:49]
<Aleks (he/him/il/lui)> can you share the full message before/after "The following signatures couldn't be verified" etc
[16:14:29]
<Lasse Gismo> W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 62D54FD4003F6525
[16:16:28]
<FbIN> > W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 62D54FD4003F6525
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/yarn.gpg > /dev/null
[16:16:54]
<FbIN> Run this Lasse Gismo, and then run the apt-update or apt-get update
[16:17:23]
<FbIN> More: https://forum.yunohost.org/t/php-repo-key-expired-solved/41499
[16:17:47]
<Aleks (he/him/il/lui)> hmokay so that's about the yarn repo but that seems unrelated to the issue during your app upgrade which is more about Sury (the PHP repo basically), `Failed to fetch https://packages.sury.org/php/pool/main/p/php8.4/php8.4-bcmath_8.4.17-1%2b0%7e20260118.40%2bdebian12%7e1.gbpd1ab00_arm64.deb 404 Not Found [IP: 2a04:4e42:1::820 443]`
[16:17:49]
<Aleks (he/him/il/lui)> are there any other issue during the `apt update` ?
[16:21:01]
<Lasse Gismo> will run the curl stuff and come back
[16:21:04]
<Lasse Gismo> Err:6 https://dl.yarnpkg.com/debian stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 62D54FD4003F6525
Err:7 https://packages.sury.org/php bookworm InRelease
The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <deb@sury.org>
[16:21:05]
<Lasse Gismo> this two:
[16:21:42]
<FbIN> > Err:6 https://dl.yarnpkg.com/debian stable InRelease
> The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 62D54FD4003F6525
> Err:7 https://packages.sury.org/php bookworm InRelease
> The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <deb@sury.org>
>
Same link, I gave, see the PHP one is also given there.
[16:23:22]
<FbIN> > hmokay so that's about the yarn repo but that seems unrelated to the issue during your app upgrade which is more about Sury (the PHP repo basically), `Failed to fetch https://packages.sury.org/php/pool/main/p/php8.4/php8.4-bcmath_8.4.17-1%2b0%7e20260118.40%2bdebian12%7e1.gbpd1ab00_arm64.deb 404 Not Found [IP: 2a04:4e42:1::820 443]`
Seems to have been removed. I can see the 20260507 as the latest.
Yup even 8.5 is 20260507 only.
[16:24:19]
<Lasse Gismo> Err:7 https://packages.sury.org/php bookworm InRelease
The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <deb@sury.org>
Fetched 16.5 kB in 6s (2,985 B/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.sury.org/php bookworm InRelease: The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <deb@sury.org>
W: Failed to fetch https://packages.sury.org/php/dists/bookworm/InRelease The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <deb@sury.org>
W: Some index files failed to download. They have been ignored, or old ones used instead.
[16:24:21]
<Lasse Gismo> output from "apt-get update --fix-missing":
[16:27:38]
<FbIN> apt autoremove --purge && sudo apt clean
[16:28:12]
<FbIN> apt clean will remove everything in cache folders.
[16:28:27]
<Lasse Gismo> after php curl, apt-get update --fix missing finished without error
[16:28:29]
<Lasse Gismo> should I start next nextcloud update or is there anything else I can check B4?
[16:28:50]
<FbIN> > after php curl, apt-get update --fix missing finished without error
great
[16:29:14]
<FbIN> > should I start next nextcloud update or is there anything else I can check B4?
just run autoclean and autoremove ones. Then run an update/upgrade for NC
[16:31:43]
<Lasse Gismo> 0 upgraded, 0 newly installed, 0 to remove and 53 not upgraded
[16:31:43]
<Lasse Gismo> 👍️
[16:32:35]
<FbIN> > 0 upgraded, 0 newly installed, 0 to remove and 53 not upgraded
for the 53, check with apt list --upgradable
[16:33:54]
<FbIN> & suggest run from from either cli or via UI the upgrades. There have been several vulnerability fixes for various packages.
[16:33:55]
<FbIN> https://doc.yunohost.org/en/admin/upgrade/
[16:51:14]
<Lasse Gismo> NC update is running further with good hope...
[16:52:15]
<FbIN> > NC update is running further with good hope...
glad to hear it. :)
[16:55:42]
<Lasse Gismo> actually there are 50 new php packages to be upgraded and NC finishes well
[16:56:14]
<Lasse Gismo> next thing will be my earlier failed friendica update, gues it's depency on php was fixed during our session
[16:56:16]
<Lasse Gismo> always great to ask for help here 👍️
[16:58:53]
<chankalan> Bonjour, je cherche un peu d'aide devant une mise à jour en échec de nextcloud, est-ce la config de nextcloud qui est perdue ? https://paste.yunohost.org/raw/nopacozivo Merci :o)
[16:59:04]
<Aleks (he/him/il/lui)> `File or folder '/etc/php/8.3/fpm/pool.d/nextcloud.conf' to be backed up does not exist`
[16:59:07]
<Aleks (he/him/il/lui)> @_@
[16:59:12]
<Aleks (he/him/il/lui)> est-ce que tu peux partager le retour de la commande : `find /etc/php -name "nextcloud.conf"` ?
[16:59:15]
<Aleks (he/him/il/lui)> t'as fait un autre truc avant ça ? (genre une tentative d'upgrade / restore qui aurait échoué en chemin)
[16:59:34]
<FbIN> > always great to ask for help here 👍️
Anytime. :)
[16:59:50]
<FbIN> > actually there are 50 new php packages to be upgraded and NC finishes well
yes, all had a lot of fixes and vul fixes too
[16:59:57]
<FbIN> *vulnerability
[17:00:25]
<FbIN> > t'as fait un autre truc avant ça ? (genre une tentative d'upgrade / restore qui aurait échoué en chemin)
Sorry, do not understand french
[17:08:08]
<Aleks (he/him/il/lui)> (this is for chankalan )
[17:11:30]
<Lasse Gismo> and friendica is updated too 😍
[17:12:14]
<Lasse Gismo> bye then and have a nice time ahead
[18:07:14]
<FbIN> > and friendica is updated too 😍
Perfect. 🙃
[18:07:26]
<FbIN> > (this is for chankalan )
Ohh okay.
[18:20:06]
<chankalan> /etc/php/7.3/fpm/pool.d/nextcloud.conf
[18:20:22]
<Aleks (he/him/il/lui)> hmoké so it is here x_X
[18:20:35]
<Aleks (he/him/il/lui)> or could it be that it's a brokn symlkink somehow ?
[18:20:40]
<chankalan> donc je peux le copier/coller dans /etc/php/8.3/pool.d
[18:20:47]
<Aleks (he/him/il/lui)> can you check the output of `ls -l /etc/php/7.3/fpm/pool.d/nextcloud.conf` ?
[18:20:52]
<Aleks (he/him/il/lui)> ah, 7.3 instead of 8.3
[18:20:55]
<Aleks (he/him/il/lui)> i suppose, but still weird that the 8.3 version doesn't exist ...
[18:36:39]
<Aleks (he/him/il/lui)> can you elaborate the context around the upgrade attempt, as mentioned previously, could it be that you tried another upgrade / backup / restore previusly and somehow the upgrade / backup or restore was interrupted before properly completing or something
[18:40:11]
<chankalan> yep, a previous backup was attempt this morning : https://paste.yunohost.org/raw/opaholulik
[18:41:13]
<Aleks (he/him/il/lui)> soooo i would assume the backup was not properly restored entirely after this upgrade attempt ?
[18:41:15]
<Aleks (he/him/il/lui)> (i'm trying to understand how we ended up in this situation in the first place)
[18:59:33]
<Aleks (he/him/il/lui)> anyway, backingup/restoring this file is not really relevant anyway because it is regenerated during restore : https://github.com/YunoHost-Apps/nextcloud_ynh/blob/master/scripts/restore#L32-L34
[18:59:36]
<Aleks (he/him/il/lui)> i suppose that's somewhat useful for people that manually tweaked the file because they'll get a warning and diff etc
[18:59:41]
<Aleks (he/him/il/lui)> anyway you can also just `sudo touch /etc/php/8.3/fpm/pool.d/nextcloud.conf`, that will create an empty file (and in the meantime nextcloud is probably not working properly) but it'll be regenerated during the upgrade or restore
[18:59:44]
<chankalan> nextcloud is already broken, and php 8.4 doesn't seem to be installed... is it worth to try that ?
[18:59:52]
<chankalan> ah but 8.3...
[19:00:00]
<Aleks (he/him/il/lui)> 8.4 will be installed during the upgrade if it's needed
[19:41:02]
<chankalan> 8.4 is needed but doesn't work, like in the previous log : https://paste.yunohost.org/raw/opaholulik
[19:55:03]
<Aleks (he/him/il/lui)> Mokay that's a 404 error on sury(php) packages similar to the person earlier, are there errors or warning when you run 'sudo apt update' ?
[20:05:07]
<chankalan> https://paste.yunohost.org/kazekadumi.apache
[20:05:18]
<Aleks (he/him/il/lui)> merf i don't know why the regen-conf didn't automatically fix this, but you can apply the same two fixes as in https://forum.yunohost.org/t/php-repo-key-expired-solved/41499
```
curl -sS https://packages.sury.org/php/apt.gpg | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/extra_php_version.gpg > /dev/null
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/yarn.gpg > /dev/null
```
[20:05:21]
<Aleks (he/him/il/lui)> then run `sudo apt update`, then retry the nextcloud upgrade
[20:05:30]
<chankalan> there is no more error after `apt update`, this is ok, but the nextcloud upgrade stay by the step : File or folder '/etc/php/8.3/fpm/pool.d/nextcloud.conf' to be backed up does not exist
[20:05:32]
<chankalan> I return to the ‘sudo touch /etc/php/8.3/fpm/pool.d/nextcloud.conf‘
[20:11:16]
<Moté> Bonsoir ! J’ai CrowdSec qui a ban les IP de Yunohost (notamment le catalogue d’applications). En regardant l’historique, je vois que les IP essayent de se connecter en SSH. C’est normal ? C’est pour le diagnostic ?
[20:24:25]
<Moté> Bon, je ne sais pas bien pourquoi, mais CrowdSec classe le diagnostic dans "postfix spam", et se fait ban
[20:24:55]
<Aleks (he/him/il/lui)> mouaip le diagnostic de yunohost tente d'ouvrir un socket TCP depuis une autre machine (le "serveur" de diagnostique) du coup effectivement ça peut être interprété comme une activité malveillante par certains outils
[20:31:35]
<Moté> C'est étrange, ça ne me le faisait pas avant que je déménage le serveur
[20:33:28]
<Moté> Bon, allez, hop, dans la whitelist
[20:33:55]
<chankalan> and then, we've got it ! thanks Aleks ! \o/ all is up to date !
[20:38:25]
<Moté> > I return to the ‘sudo touch /etc/php/8.3/fpm/pool.d/nextcloud.conf‘
Maybe you should regenerate yunohost confs for this one
[20:41:24]
<Aleks (he/him/il/lui)> the "core" regenconf doesnt handle app confs
[20:41:25]
<Aleks (he/him/il/lui)> app packaging v3 will have a better system where you'll be able to regen app confs
[20:45:36]
<otm33> Ce problème de conf php "disparue" est très fréquent ces derniers temps.