Omnibus gemspec in our fork is not commited

When running bundle install from our master branch, our omnibus fork has changes in omnibus.gemspec that are not commited. We need to find out why and make this change.

@balasankarc can you check this one please?

@marin Upon checking, bundle install does that for every gem. It parses the gemspec file, expands the statements (like git ls ... for listing files etc) and freezes the result (and strings etc.). It doesn't alter the working of the gem. Actually, it does that for all kinds of installations, not only the ones sourced from git. For the ones sourced from rubygems.org, the modified gemspecs are stored in .bundle/ruby/2.3.0/specifications, so they don't fall under git diff's watch. But for the ones sourced from git, the existing gemspec is modified.

assigned to @balasankarc

This is actually an expected behavior of bundle install. Closing as there is nothing actionable here.

closed