Open desaperados opened 9 years ago
Some weird caching issue here
Would suggest that this build pack has issues with CACHE_DIR
I am only able to successfully deploy after purging the cache.
Have tracked this down to being an issue with a non-relase version of the rgeo gem - we had rgeo locked to a particular commit in the Gemfile due to the last release being quite a bit behind master.
It would seem that the build pack doesn't correctly handle caching of non-releases.
Now using rgeo 0.4.0 which is working as expected. The issue remains but will only affect anyone trying to use a non-release version of the gem.
Thank you -- I had this exact same problem from pinning rgeo to a specific commit. Purging fixed the issue I was seeing after upgrading to rgeo 0.4.0.
I'm able to deploy first time to a new cedar-14 heroku application and to an upgraded cedar-14 application after running
heroku repo:purge_cache
. However, subsequent deploys are failing every time with output as below.I'm able only able to deploy with this build pack after running
heroku repo:purge_cache
which suggests a caching issue. Any builds I try without clearing the build cache are failing as below: