Closed (fixed)
Project:
Opigno LMS (Community version)
Version:
8.x-1.0-beta1
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
31 Jan 2019 at 16:51 UTC
Updated:
1 Jul 2019 at 09:09 UTC
Jump to comment: Most recent
Comments
Comment #2
axelmHi
The update is only possible from the release candidate, not the beta version.
I case you are using the RC or a later version, then you should check our documentation for composer update
https://opigno.atlassian.net/wiki/spaces/OUM20/pages/363134999/Upgrade+w...
Comment #3
joachim namysloThe installation profile is (opigno_lms-8.x-1.0) update to new core isn't possible.
Comment #4
mmjvb commentedYou forgot to mention:
Which means it runs composer update (without packages mentioned).
opigno/opigno-composer is a project type package, used to create-project. After which it refers to your project. There is no update for project. You can only create-project with a new version.
Each version of opigno/opigno-composer requires exact versions of drupal/core and opigno/opigno_lms. Those exact versions pin almost everything down. composer update doesn't find anything within the version constraints that it can update. Which is what it told you.
As far as drupal/core is concerned, suggest to: composer require drupal/core:~8.6.4 --no-update, which requires you to run with --no-install on create-project. That will give you the current version, based on semver, that is what you should get. Obviously, you need a composer install after the composer require.
Concerning opigno/opigno_lms suggest to follow instructions provided. Apart from the correction For drupal/core. Consider it a mistake to pin it on exact version.
Comment #5
joachim namysloWell the point is. I've reinstalled opigno from the repo named above, again.
After a while the Core gets updated again and now the effect is the same, if composer update is used. Some components get updated but the core version of the package is still minor than the last core update published on d.o.
Maybe there is a reason for this but I bet if I install opigno to a new folder by using the same repo, again, everything will be fine again.
And in this case that's not a feature but a bug.
I'll try it again within the next few weeks and report an other issue with before after screenshots and reproducing procedure as soon as I have some time to do so.
Comment #6
joachim namysloOk there is no bug. Maybe it is to hard for some body to give simple answers. So I answer my self for reference here:
1. Go to your opigno install root for
2. Enter
composer require Drupal/core:x.x.xWhile x.x.x is the Version number of Drupal.This is valid for any security patch upcoming in the feature.
Opigno in general could be updated with
composer updateif there was made an update to the packaging.org Repository Opigno/Opigno-ComposerThis will be mentioned on the releases tab on d.o and on packagegist.org if you find the release page there by using any search engine
You should take your time and add this to documentation.
The answers above hadn't helped that much.
Comment #7
mmjvb commentedSounds like you still don't understand. Your answer is incorrect. Suggest to read my answer again.
Comment #8
joachim namyslo@mmjvb
Maybe someone else may understand the concern better than I do.
For me the trick above did the security patch to Drupal 8.6.10 after the composer package was used.
Maybe that composer will not do anything with this package until it gets a new version. Or untill a new Drupal core version is given to composer, when you create a new project by using this package. But this is just not the concern here. Maybe I should just change the heading to make it clear
I am still not sure how to do it correctly
composer require drupal/core
composer install
What does :~8.6.4 mean?
If drupal/core is greater than 8.6 4 than install 8.6.x ?
Comment #9
joachim namysloComment #10
mmjvb commentedAs mentioned: `composer require drupal/core:~8.6.4` should be used. The ~8.6.4 will allow `composer update drupal/core` for every release within 8.6. That means when you are prepared to update to 8.7 you would need to `composer require drupal/core:~8.7.1`, assuming you don't want to jump into 8.7.0.
For those wanting to live dangerously, they could use `composer require drupal/core:^8.6.4`. Allowing for `composer update drupal/core` for any 8. release.
Again, you can't do anything with this package "opigno/opigno-composer". The composer create-project clones it and runs composer install with that clone. No way to update is provided. It is the same problem all those people using drupal/drupal ran into. Not designed to update! For drupal/drupal it was drupal/core, for opigno/opigno-composer it is whatever is in it. Same thing for any of the other packages of this type. Only Opigno (the creator of the package) can say what needs to be done to update to a new version of opigno/opigno-composer. AFAIK, there is no upgrade provided.
Obviously, your installation can be upgraded. Fortunately, drupal/core can and should. Which is why I consider it a bug to pin it to an exact version. With Semantic Versioning in mind `composer update drupal/core` should have updated your installation to 8.6.10.
Comment #11
axelmHello,
A new version of Opigno with Drupal core 8.6.10 was released yesterday. Video module also required a security update.
Please refer to our online documentation for upgrade: https://opigno.atlassian.net/wiki/spaces/OUM20/pages/363134999/Upgrade+w...
Comment #12
mmjvb commentedConsider the support request dealt with, set Status to Fixed.
For generic information on Composer see the documentation on their website.
Comment #14
aaronbaumanIf, like me, you're simply looking for the latest version of composer.json to update your opigno install, you can find it here:
https://bitbucket.org/opigno/opigno-composer/src/master/composer.json