Cloudron 3.3 released
-
@ahelton Upstream wallabag is close to fixing the issue. You can track it at https://github.com/wallabag/wallabag/pull/3758
-
@saglagla https://github.com/wallabag/wallabag/issues/3739 also needs to be fixed. It looks like only wallabag 3.4 will support it.
@girish said in Cloudron 3.3 released:
@saglagla https://github.com/wallabag/wallabag/issues/3739 also needs to be fixed. It looks like only wallabag 3.4 will support it.
But that's mean there is some issue to migrate only ?
If I backup Wallabag, destroy it. Upgrade and then re-install, it will work ?Or there is an issue between wallabag and cloudron > 3.2.3 ?
-
@saglagla the issue is the Postgresql version. The current wallabag is not yet compatible with the version of Postgres Cloudron > 3.2.3 ships. So reinstallation would not work. This is the reason we block the Cloudron update for instances which have wallabag installed.
-
@saglagla the issue is the Postgresql version. The current wallabag is not yet compatible with the version of Postgres Cloudron > 3.2.3 ships. So reinstallation would not work. This is the reason we block the Cloudron update for instances which have wallabag installed.
@nebulon said in Cloudron 3.3 released:
(...) The current wallabag is not yet compatible with the version of Postgres Cloudron > 3.2.3 ships. So reinstallation would not work. This is the reason we block the Cloudron update for instances which have wallabag installed.
It looks like making Wallabag support a newer version of Postgresql is literally a single-line patch.
Might it make sense to carry this as a custom patch for now and be done with it?
-
Looks like the patch that @jk referred to has been merged into Wallabag for 2.4, it would be nice to have this patched in the Cloudron version.
I've submitted a Merge Request for the wallabag-app here: https://git.cloudron.io/cloudron/wallabag-app/merge_requests/1
Is it possible to get this merged so that we can upgrade Cloudron?
