specify Active Support version on cap deploy:setup

[Jamie Orchard-Hays]

I’m upgrading a db server and am using brightbox21 ruby. Somewhere, ActiveSupport is loading the latest (5.x) version, but I need a 4.x version. Is there a way to specify this?

Cheers,

Jamie

[Jamie Orchard-Hays]

BUMP. Wondering if Rails Machine still monitors this group.

[Bryan Traywick]

Hey Jamie,

Sorry I forgot to respond to this last week. Unfortunately we’ve seen this a couple times since the Rails 5.x release. The easiest way to workaround it is to first run `cap <stage> shell` and manually install the 4.x version of ActiveSupport with `sudo gem install activesupport -v ‘~> 4’`. You should then be able to successfully run your `deploy:setup` or `ruby:upgrade` task. I’ll take some time later today or tomorrow to setup a test VM and test out some ideas I have on how to fix this. I either need to modify the `shadow_puppet` to depend on `activesupport <= 4.x` for greater compatibility, or simply add a line to the `install_moonshine_deps` Capistrano task to install ActiveSupport 4.x for the same reason.

Thanks,
Bryan Traywick
Senior SRE at Rails Machine

> --
> You received this message because you are subscribed to the Google Groups "Moonshine" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to railsmachine-moon...@googlegroups.com.
> To post to this group, send email to railsmachin...@googlegroups.com.
> Visit this group at https://groups.google.com/group/railsmachine-moonshine.
> For more options, visit https://groups.google.com/d/optout.

[Jamie Orchard-Hays]

So, I’m guessing run the ruby installation task first?

[Bryan Traywick]

Hey Jamie,

I just released a new version of shadow_puppet that depends on ActiveSupport < 5.0 and updated moonshine so that it installs that version now. Try updating moonshine to the latest version and running the upgrade again. Let me know if you have any other issues.

Thanks,
Bryan

[Jamie Orchard-Hays]

Cheers, Bryan. I should be working on something related to this in the next few work days, so will definitely update and use the new code.

Jamie

[Jamie Orchard-Hays]

Good news, cap deploy:setup went fine for deploying a new server today .

However, on cap deploy with rails 4.2.7.1, passenger 5.0.30, and Mongodb. I got ruby minimum version error, due to a rack dependency. I haven’t traced where this is coming from yet, as the version of rack with rails doesn’t ask for this.

Error: Could not update: Execution of '/usr/bin/gem install -v 5.0.30 --no-rdoc --no-ri passenger' returned 1: ERROR: Error installing passenger:
** [out :: 162.209.96.162] rack requires Ruby version >= 2.2.2.
** [out :: 162.209.96.162] Error: /Package[passenger]/ensure: change from absent to 5.0.30 failed: Could not update: Execution of '/usr/bin/gem install -v 5.0.30 --no-rdoc --no-ri passenger' returned 1: ERROR: Error installing passenger:
** [out :: 162.209.96.162] rack requires Ruby version >= 2.2.2.