Can't remove fingerprints from only *some* files about digestion HOT 2 CLOSED

I'm seeing the correct behaviour on a new Rails 3.1.0 app with the digestion and twitter-bootstrap-rails gems, and config.assets.digest_exclusions << /fontawesome/ added to config/environments/production.rb. Are there any other gems that could be interfering with the compilation process?

I'd strongly recommend upgrading from 3.1.0 though if at all possible. In later versions, the digestion gem is unnecessary as both fingerprinted and non-fingerprinted assets are compiled, not to mention the security fixes in Rails itself.

from digestion.

I wouldn't have thought there'd be a problem with other gems, but the ones I have relevant to assets (and their dependencies) are:

sprockets (2.0.3)
  hike (1.2.1)
  rack (1.3.6)
  tilt (1.3.3)
jquery-rails (1.0.19)
  thor (0.14.6)
sass-rails (3.1.6)
  sass (3.1.15)
coffee-rails (3.1.1)
  coffee-script (2.2.0)
    coffee-script-source (1.2.0)
    execjs (1.3.0)
      multi_json (1.3.6)
uglifier (1.2.3)
therubyracer (0.9.9)
  libv8 (3.3.10.4)
twitter-bootstrap-rails (2.0.6)
  less-rails (2.2.3)
    less (2.2.1)
      commonjs (0.2.6)
digestion (1.2.1)

Any known issues with those...?

Anyway, what I might do is compile the assets without fingerprinting, commit just the fontawesome stuff, and then I can revert those back whenever I compile them again. It's a bit of a hack, but I think it'll work.

from digestion.