Hi Marion,

sorry for the issues and inconveniences in the upgrade process.

We encountered the database issue ourselves, which is a side effect caused by the renaming of the previous `openproject-ce` package to `openproject`.
The installer responsible for creating the database automatically sets the username and database name to this application name, which causes a separate database to be created.

We are currently fixing this issue for future installation, for the time being we have extended the upgrade path with a workaround to this issue.

https://github.com/opf/openproject/blob/release/5.0/doc/operation_guides/packager/upgrade-guide.md#migrating-from-openproject-community-edition-42

Please let me know if this workaround resolves the issue for you.

As you may no longer be able to run `openproject-ce` from step 3, you can get the database connection details from `/etc/openproject/conf.d/database`

Best,
Oliver

Thanks Oliver!

I don’t have access to my test system right now, but the db handling looks better. Will try later today.

Can you confirm the package repo?

https://deb.packager.io/gh/opf/openproject-ce trusty stable/5

Maybe more like
https://deb.packager.io/gh/opf/openproject trusty release/5.0 ?
But in contrary to the url there is the wrong package in it?

Thanks!
M.

Hi Marion,

another good point to extend the documentation with.

The release branches are part of our documentation workflow. We will have release branches for all minor versions, that is, e.g., release/5.0, release/5.1, etc.

The stable/5 branch will be set to the latest stable tagged release (5.0.0 currently, 5.0.1 in the next hours/days, 5.0.2, … 5.1, 5.2, ….).
This way, we want to provide the users with the latest stable release in the current major version up until the next major, possbily breaking version (6.0).

We do not officially promote packages for release/5.0 , since their upgrade path is limited to 5.0.1 - 5.0.x, but it’s still possible to install them manually.
Once we push out our fix concerning the database issue, it will be available both on release/5.0 and stable/5 at roughly the same moment.

Does this information help clear up the decisions for the two branches?

If you have any further questions or suggestions to improve the documentation or the release process, let us know! We appreciate all feedback.

Best,
Oliver

Oliver Günther wrote:

Please let me know if this workaround resolves the issue for you.

Works! Many thanks!

M.

Hi Marion,

thanks for the update. Great to hear the workaround works for you.

In the meantime, we have resolved the issue [1 for the interested] and will publish that fix amongst other things in 5.0.1., likely released today.
We’re removing the workaround sections after that, since the upgrade should just work after that.

Thanks again for the report.
Best,
Oliver

[1] https://github.com/pkgr/addon-mysql/commit/041b16b6d3dbed135391aa61f8c6497fe79a3ae9