Arch Linux

Description:

Having ruby-sass-listen installed prevents me from deploying Ruby/Bundler projects to other platforms because of broken gem dependencies.

Additional info:

ruby-sass-listen 4.0.0-5

Steps to reproduce:

1. Install ruby-bundler and ruby-sass-listen via pacman
2. Run `bundle install` against the attached Gemfile
3. Expect for a Gemfile.lock to be produced
4. Remove ruby-sass-listen via pacman
5. Run `bundle install` against the same Gemfile
6. Expect for the operation to succeed

What happens instead?

The bundle install operation fails with the following output:

Fetching sass-listen 4.0.0
Downloading sass-listen-4.0.0 revealed dependencies not in the API or the lockfile (rb-fsevent (>= 0.9.4, ~> 0.9), rb-inotify (>= 0.9.7, ~> 0.9)).
Either installing with `--full-index` or running `bundle update sass-listen` should fix the problem.

In Gemfile:
sass was resolved to 3.5.7, which depends on
sass-listen

Why did this happen?

In the PKGBUILD for ruby-sass-listen, optional OSX dependencies (rb-fsevent) are artificially removed. This is problematic because if a Gemfile.lock is created when the arch-packaged version of ruby-sass-listen is installed, it will respect the (now broken) dependency list and place that information in Gemfile.lock.

After removing ruby-sass-listen and running bundle install for the second time, Bundler will look at the correct, unmodified dependency list and bail out because 1. a lockfile already exists, but 2. the dependency list is not what bundler expected.