Upgrading an application via the built-in update system / Mise à niveau d'une application via le système de mise à jour intégré

Support apps
, ,
1

What app is this about, and its version: Any
What YunoHost version are you running: 12.1.37
What type of hardware are you using: VPS bought online

Describe your issue

:united_kingdom: Hello everyone, and sorry if my question is silly, I’ve tried searching the forum but haven’t found an answer.

Regarding application updates, should we only use YunoHost’s update function, or can we also perform updates via the built-in application update system?

I’m asking out of curiosity because I’m currently installing Paheko. Through the YunoHost catalog, I have version 1.3.17.1~ynh1. And in the Paheko interface, it’s offering me the option to install version 1.3.18 using the built-in system.

Logically, I’m thinking I absolutely shouldn’t do that. But perhaps it’s possible?

This issue might come up again for a new WordPress site that I’m planning to put on my YunoHost instance.

And since I might be sharing administrative rights on the apps, I’m worried that others might be tempted to click “Download update” or “Apply update” thinking they’re doing the right thing.

Thank you in advance for your insight,

C.

:france: Bonjour la communauté et désolé si ma question est bête, j’essaie de chercher sur le forum et je ne trouve pas de réponse.

Pour la mise à jour des applications, est-ce que l’on ne doit utiliser que la fonction de mise à jour de YunoHost, ou est-ce que l’on peut également effectuer les mises à jour via le système de mise à jour intégré des applications ?

Je me pose la question par curiosité car je suis en train d’installer Paheko, via le catalogue YunoHost j’ai la version 1.3.17.1~ynh1. Et dans l’interface de Paheko il m’est proposé d’installer la version 1.3.18 avec le système intégré.

Dans ma logique je me dis de ne surtout pas le faire. Mais peut-être que c’est possible ?

La problématique risque de se reposer à moi pour un nouveau site Wordpress que j’envisage de mettre sur mon instance YunoHost.

Et je risque de partager des droits d’administration sur les applis, je me dis que les autres sont susceptibles d’être tentés de cliquer sur “Télécharger la mise à jour” ou “Appliquer la mise à jour” en pensant bien faire.

En vous remerciant par avance pour votre éclairage,

C.

2

I don’t know Paheko but in general it’s advised to upgrade from package update only, and not from inside an app.

Sometimes it’s possible to disable an app upgrade from inside the app (like I did here for example), but not always. Should be checked for Paheko and Wordpress.

1 Like
3

In addition, I can only encourage you to check for pending upgrades in the corresponding git repo, for example here for Paheko : Pull requests · YunoHost-Apps/paheko_ynh · GitHub

Minor upgrades should be mostly straightforward and boil down to upgrading the source URL + sha256 in the manifest : paheko_ynh/manifest.toml at master · YunoHost-Apps/paheko_ynh · GitHub .. in fact, for plenty of packages, we now have automatic upgrades monitoring the upstream repo, and a corresponding pull request should be created by a bot the next day of the release.

Yet we need humans to properly validate and test those.

Anyway in the case of Paheko 12.1.38 there is this open PR which could use some feedback new release 1.3.18 by rodinux · Pull Request #106 · YunoHost-Apps/paheko_ynh · GitHub

In an ideal world, every YunoHost admin can participate in keeping the packages up to date, properly report issues so they can be debugged, which in turns profit to everybody …

1 Like
4
1 Like
5

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.