Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#52500 - [gitlab] Bundler update broke rake
Attached to Project:
Community Packages
Opened by Jonas Heinrich (onny) - Wednesday, 11 January 2017, 21:15 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 15 January 2017, 23:14 GMT
Opened by Jonas Heinrich (onny) - Wednesday, 11 January 2017, 21:15 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 15 January 2017, 23:14 GMT
|
DetailsDescription:
Somehow the ruby-bundler update broke rake: [2017-01-11 19:50] [ALPM] upgraded ruby-bundler (1.13.7-1 -> 1.13.7-2) [2017-01-11 19:51] [ALPM] upgraded gitlab (8.15.2-1 -> 8.15.3-1) onny@http-new /usr/share/webapps/gitlab % sudo -u gitlab bundle exec rake db:migrate RAILS_ENV=production Your bundle is locked to rake (10.5.0), but that version could not be found in any of the sources listed in your Gemfile. If you haven't changed sources, that means the author of rake (10.5.0) has removed it. You'll need to update your bundle to a different version of rake (10.5.0) that hasn't been removed in order to install. Run `bundle install` to install missing gems. Best regards, Jonas |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Sunday, 15 January 2017, 23:14 GMT
Reason for closing: Fixed
Sunday, 15 January 2017, 23:14 GMT
Reason for closing: Fixed
This temporary solves the problem until we get support for Ruby 2.4
Official docs say Ruby 2.3 is the latest supported:
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md
Official bug report:
https://gitlab.com/gitlab-org/gitlab-ce/issues/26084