Created attachment 166718 [details]
fix postgresql adapter through Gemfile patch...
Patch attached unbreaks redmine after rubygem-pg was updated in r401667.
Please note that Torsten Zuehlsdorff has prepared a patch to upgrade redmine to 3.2.0, which will probably fix this, too.
Where do I find it?
I've put it on http://people.freebsd.org/~pi/misc/redmine.diff
Is the plan to deprecate Redmine 2.x completely,
or rather move the port to www/redmine2, then
copy that to www/redmine and apply that patch?
Nothing is decided yet. What would you prefer ?
I'm not much personally invested - especially if I can install Redmine 3 as easy as I can Redmine 2.
I have a hunch some users might (for whatever reason) find it convenient not to upgrade to 3.x for the time being or at least until they've been able to check whether migrating their DB to it is feasible&simple.
When do you plan to merge Torsten's patch, roughly?
Torsten's is on vacation this week, and I'll have loads of work @dayjob the next week, so I'm not promising anything! If he submits the diff to a PR, anyone can work on it. It just happens that I need to do some redmine and found the available port old, and Torsten says he planned to work on it to get rid of some old ruby stuff.
Makes sense. :-)
My problem is that until Redmine 3, or this patch, lands, I'll need a patched portstree to install Redmine 2 via Ansible --
and that I was hoping we could get this break-fix in, so that at least I don't have to maintain this breakfix in a local portstree, when other users could benefit from it too.
Because, currently, if you *do* want to use Redmine 2.x with Postgresql, it *is* broken since the rubygem-pg upgrade in r401667,
but can be fixed with the patch attached.
A commit references this bug:
Date: Sat Feb 20 15:56:32 UTC 2016
New revision: 409250
- Fix postgres support for redmine2
Submitted by: Johannes Jost Meixner <email@example.com>