Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #6740

Closed
Open
Created Apr 09, 2014 by Administrator@rootOwner

Suggestion: Upgrade some dependencies of gitlab

Created by: 123Haynes

Disclaimer: I'm not a ruby developer, so some things may be plain stupid of me. Please bear with me.

Hello,

I just saw that ruby 2.1.1 has been out for some months now. But the install instructions still require ruby 2.0 p353. Is there any particular reason for this? Has anybody tested Gitlab with that version already?

I tried to build it after updating ruby, but i'm currently stuck at the markup gem. For some reasons i don't know git refused to find the commit mentioned in the gemfile for this. So i updated the gemfile to the current commit. (v.1.0.0 on our fork. Version 1.0.2 has been released by github btw ;) ) That resolves that problem but opens up another :/ It seems that the gem gitlab-gollum-lib requires a version of the markup gem that's lower than 1.0.0. If someone tells me how to work around that issue, i'll try to test gitlab with ruby 2.1.1 :) Easiest solution i can think of would be to set the required version <=1.0.2 but maybe there is a good reason for it to stay like it is?

All in all i simply suggest to update the dependencies of gitlab since several new versions have been released.

kind regards, Haynes

Assignee
Assign to
Time tracking