Name |
Last commit
|
Last Update |
---|---|---|
cucumber | ||
features | ||
gemfiles | ||
lib | ||
shoulda_macros | ||
spec | ||
.gitignore | ||
.travis.yml | ||
Appraisals | ||
CONTRIBUTING.md | ||
Gemfile | ||
LICENSE | ||
NEWS | ||
README.md | ||
RUNNING_TESTS.md | ||
Rakefile | ||
UPGRADING | ||
paperclip.gemspec |
Turns out that between fog 1.22.0 and fog 1.25.0, there was a change to how fog builds S3 expiring URLs. This changes to test to be the common point between the two versions. All we need to do here is make sure that the expiring URL is being constructed. In the process, this also updates all the appraisal-generated Gemfiles. Also, in the process, this meant I had to take away the builder version restriction. This was put in so that `bundle`ing wouldn't take forever, but I'm unsire whether this needed to happen with this version or if builder just needed to be separate from the Gemfile. I'm commimtting this and asking the people who reported the problem. If you don't see a revet commit, everything was fine.
Name |
Last commit
|
Last Update |
---|---|---|
cucumber | Loading commit data... | |
features | Loading commit data... | |
gemfiles | Loading commit data... | |
lib | Loading commit data... | |
shoulda_macros | Loading commit data... | |
spec | Loading commit data... | |
.gitignore | Loading commit data... | |
.travis.yml | Loading commit data... | |
Appraisals | Loading commit data... | |
CONTRIBUTING.md | Loading commit data... | |
Gemfile | Loading commit data... | |
LICENSE | Loading commit data... | |
NEWS | Loading commit data... | |
README.md | Loading commit data... | |
RUNNING_TESTS.md | Loading commit data... | |
Rakefile | Loading commit data... | |
UPGRADING | Loading commit data... | |
paperclip.gemspec | Loading commit data... |