Hi,

do you use the packaged installation? If so, upgrading should be nothing more than running

sudo apt-get update
sudo apt-get install --only-upgrade openproject

It is not the case for the jump from 5.0.7 to 5.0.11, but as the release may contain new migrations or options to the wizard (less likely so in a patch release), you should also run

sudo openproject configure

Best,

Oliver

Dear Oliver,

Thanks for the reply.

My Openproject 5.0.7 was not using packaged install. I’m using manual installation.

In this case, how to do the upgrade.

Again, Thanks.

Choong Leng

In a manual installation, you’ll need to fetch the latest release - Since you probably cloned the repository using Git, you can simply checkout the stable/5 branch, which always points to the latest released version.

Lastly, install any pending migrations and precompile assets.

RAILS_ENV="production" bundle exec rake db:migrate
RAILS_ENV="production" bundle exec rake db:seed
RAILS_ENV="production" bundle exec rake assets:precompile

Thanks Oliver. Get it upgraded to v5.0.13

Hi,

I get the following error while running assets:precompile (migrate and seed ran through):

C:/Bitnami/openproject-5.0.7-1/ruby/lib/ruby/2.1.0/dl.rb:8:in `<top (required)>’ : DL is deprecated, please use Fiddle (StandardWarning)
$(npm bin)/webpack —config webpack.config.js rake aborted!
Command failed with status (127): [$(npm bin)/webpack —config webpack.config…]
C:/Bitnami/openproject-5.0.7-1/apps/openproject/htdocs/lib/tasks/assets.rake:48: in `block (3 levels) in <top (required)>’
C:/Bitnami/openproject-5.0.7-1/apps/openproject/htdocs/lib/tasks/assets.rake:47: in `chdir’
C:/Bitnami/openproject-5.0.7-1/apps/openproject/htdocs/lib/tasks/assets.rake:47: in `block (2 levels) in <top (required)>’
Tasks: TOP => assets:precompile => assets:compile_environment => assets:webpack
(See full trace by running task with —trace)

Is there a workaround without having to fixw node (I already tried that and ran into Python / MSBuild problems).

Regards and thanks,
Daniel