[Gitlab] Current Status of the port

[Torsten Zuehlsdorff]

On 05.08.2015 19:10, Steve Wills wrote:

>>>> I will have a look at it. Is there anything in "Admin Area" -> "Logs"
>>>> which could be helpful?
>>>
>>> No, it looks to be a javascript issue, clicking the button doesn't even trigger
>>> any sort of http request, it just does nothing.
>>
>> I think I may have figured out the issue. jquery 4.x isn't compatible with
>> rails 4.1, it needs 4.2:
>>
>> https://github.com/rails/jquery-rails/blob/master/CHANGELOG.md
>>
>> So we need jqueyr 3.1.3 and friends. I'll have a look at changing that locally to test.
>
> Looks like cal-heatmap-rails upgrade from 0.0.1 to 3.5.1 was the real issue.
> Tho I think we may want to consider dropping jquery-rails back to 3.1.3 just to
> be safe and what I said about changing ~> to => in Gemfile still applies.

Okay, i will create a port for the old jquery-rails. Currently there is 
a pending slave-port "rubygem-jquery-rails41" for GitLab. I could 
rewrite it to use 3.1.3. Or should i replace it with an explicit 
"rubygem-jquery*3*-rails41"? In this case we can omit the other one.

Also i will rework the Gemfile patches to be less optimistic.

This week i haven't much time left. I can't guarantee to get it done 
before monday. Sorry.

Greetings,
Torsten