Tried the commands you gave me, first one went through, second one returned this :
/var/www/flarum# sudo -u flarum php7.3 /var/www/flarum/composer.phar require 'flarum/core:~1.0.0' --prefer-dist --update-no-dev -a --update-with-all-dependencies -d /var/www/flarum --no-interaction
Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See https://blog.packagist.com/deprecating-composer-1-support/
./composer.json has been updated
Loading composer repositories with package information
Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See https://blog.packagist.com/deprecating-composer-1-support/
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- flarum/approval v0.1.0-beta.13 requires flarum/core ^0.1.0-beta.13 -> satisfiable by flarum/core[v0.1.0-beta.13, v0.1.0-beta.14, v0.1.0-beta.14.1, v0.1.0-beta.15, v0.1.0-beta.16] but these conflict with your requirements or minimum-stability.
- flarum/approval v0.1.0-beta.13 requires flarum/core ^0.1.0-beta.13 -> satisfiable by flarum/core[v0.1.0-beta.13, v0.1.0-beta.14, v0.1.0-beta.14.1, v0.1.0-beta.15, v0.1.0-beta.16] but these conflict with your requirements or minimum-stability.
- flarum/approval v0.1.0-beta.13 requires flarum/core ^0.1.0-beta.13 -> satisfiable by flarum/core[v0.1.0-beta.13, v0.1.0-beta.14, v0.1.0-beta.14.1, v0.1.0-beta.15, v0.1.0-beta.16] but these conflict with your requirements or minimum-stability.
- Installation request for flarum/approval (locked at v0.1.0-beta.13, requir4ed as ^0.1.0) -> satisfiable by flarum/approval[v0.1.0-beta.13].
Running update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems.
Installation failed, reverting ./composer.json to its original content.
And Flarum 1.0 update still fails the same way… I tried to tweak with composer.json (as shown in the flarum documentation) but it did not change anything so i reverted it back to original.
Since my install seems a bit sketchy, wouldn’t it be easier/safer to backup the forum files, reinstall a fresh 1.0 flarum and reinject the saved forum files ? Assuming those posts/photos/users/etc. are easily backupable and restored…
I was following the update recommandations given in the flarum documentation but with cold feet, so i did not go all the way (was afraid to lose data because of conflicts between flarum/php command lines and yunohost update processes or whatever, weird stuff happened to me before with nextcloud and i lost it all, so yeah).
That’s normal. The version is given by the package when it is processed by YunoHost. YunoHost will not update that version if you manually alter your app.
The version will be updated upon the next upgrade via the normal means.
Pour mémoire, il y a quelques mois, suite à des problèmes de connexions après une mise à jour, il avait été demandé de modifier des paramètres dans la BD :).
À noter que lorsque l’on demande de mettre le jour du système YUNOHOST, il y a cette erreur
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/extra_php_version.list:1 and /etc/apt/sources.list.d/sury.list:1
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/extra_php_version.list:1 and /etc/apt/sources.list.d/sury.list:1
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/extra_php_version.list:1 and /etc/apt/sources.list.d/sury.list:1
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/extra_php_version.list:1 and /etc/apt/sources.list.d/sury.list:1
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/extra_php_version.list:1 and /etc/apt/sources.list.d/sury.list:1
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/extra_php_version.list:1 and /etc/apt/sources.list.d/sury.list:1
Des erreurs se sont produites lors de la mise à jour du cache APT (gestionnaire de paquets Debian). Voici un extrait des lignes du fichier sources.list qui pourrait vous aider à identifier les lignes problématiques :
sources.list:deb http://deb.debian.org/debian buster main contrib non-free sources.list:deb-src http://deb.debian.org/debian buster main contrib non-free sources.list:deb http://security.debian.org/ buster/updates main contrib non-free sources.list:deb-src http://security.debian.org/ buster/updates main contrib non-free sources.list:deb http://deb.debian.org/debian buster-updates main contrib non-free sources.list:deb-src http://deb.debian.org/debian buster-updates main contrib non-free sources.list.d/sury.list:deb https://packages.sury.org/php/ buster main sources.list.d/yunohost.list:deb http://forge.yunohost.org/debian/ buster stable sources.list.d/mongodb-org-4.4.list:deb http://repo.mongodb.org/apt/debian buster/mongodb-org/4.4 main sources.list.d/influxdb.list:deb https://repos.influxdata.com/debian buster stable sources.list.d/extra_php_version.list:deb https://packages.sury.org/php/ buster main
Ce qui n’empêche pas à la fin Le catalogue des applications a été mis à jour !
J’ai une autre instance YNH aussi sur un VPS OVH, je n’ai pas cette erreur.
Nah. Adding extensions after installation just dont work. I’m upset haha. Seriously guys, please update the faq.
./composer.json has been updated
Running composer update vendor/extension --with-dependencies
Loading composer repositories with package information
Dependency “app/core” is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires vendor/extension ^0.1.1 → satisfiable by tvendor/extension.
- vendor/extension requires vendor/extension ^0.1.0-beta.10 → found bla bla but it does not match your minimum-stability.
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.