New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Private Sprockets Fork #2128
Conversation
The sprockets maintainer yanked the sprockets version we use from rubygems. It happened that I had the specific sprockets version at my harddrive. We really should update sprockets, but until this happens, the fork can be used.
I've prepared a stage. Click to open. |
@tessi the sooner we get off this shit, the better. |
@tessi, this is against the dev branch, we will probably have to get this against release/4.0 as well. |
Hi @tessi and all, Newbie here, i've been trying to install Openproject on by Debian 8 VPS and i've run into this: Bundler could not find compatible versions for gem "sprockets": I see that "The sprockets maintainer yanked the sprockets version we use from rubygems." but i've just downloaded the latest version of Openproject, is this problem still alive, is there a fix? I found one old download for the 2.2.2 but that seems to be faulty. My system: Please advise asap, much appreciated. |
Hi Astehmari, I got that exact same error a year ago and, therefore, forked sprockets and re-introduced that sprockets version. I noticed that the @opf/developers (one of the core people - can't remember who it was right now) forked my fork. So maybe something changed in the recent OpenProject versions. If you use my Sprockets fork in the Gemfile things should probably work fine, but I guess the OpenProject team has something in mind with their change. So it's probably a bug, that should get fixed. |
(and I want to stress that is is a very good idea not to use my fork and, instead, migrate OpenProject to one of the officially maintained sprockets versions which enjoys the luxury of security fixes) |
Hi @astehmari , you're probably on a 4.2 release. Please see this PR that relies on a fork of the OP developer for sprockets on 4.2: #3399 |
@oliverguenther 👍 thanks for the late reply :) |
Hi Philipp & Oliver, Thanks for getting back to me on this. I'm quite new to administering this The 2_2_2_backport2 at This fix relies on a clone of the repo to fix the branch structure.What should i do? On 1 September 2015 at 23:13, Philipp Tessenow notifications@github.com
Astehmari Batekun Executive Member T: 020 8144 1720 |
Hi Astehmari, sure, let's step back a bit to find out why this is happening to you. Did you install OP manually using the guide, or a packaged installation? |
Hi Oliver, Yes these are the instructions i am working through. The On 2 September 2015 at 06:53, Oliver Günther notifications@github.com
|
Hi everyone, Any news on this? I've been trying to showcase and explore Openproject Astehmari On 2 September 2015 at 09:19, Astehmari Batekun astehmari@gmail.com wrote:
|
Hi @astehmari , sorry for the delay. We're currently working very hard on the latest changes for a major upcoming release (5.0) and I've overlooked your last comment. That being said, I cannot reproduce your error on the current You should have these entries in your Gemfile (l. 104ff.). Please report if the specified versions do not match these below.
I'd also like to invite you to the public gitter channel, in which we may exchange information more quickly and with more members to join in: |
Hi Oliver and all, Thanks for your assistance and advise. That socket issue has now been You are currently validating against Phusion Passenger 5.0.16, located in: /home/openproject/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0/gems/passenger-5.0.16/bin/passenger Besides this Passenger installation, the following other
Please uninstall these other Passenger installations to avoid confusion or conflicts.How should i remove /home/openproject/.rbenv/shims/passenger? I think this is the final issue. Apache is viewing the correct place, just Please advise on removing passenger asap, thanks. Astehmari On 3 September 2015 at 19:54, Oliver Günther notifications@github.com
|
The sprockets maintainer yanked the sprockets version we use from rubygems.
It happened that I had the specific sprockets version at my harddrive.
We really should update sprockets, but until this happens, the fork can
be used.
It seems other people have this problem too ->https://community.openproject.org/topics/1348?page=1&per_page=200