Unfortunately, AWS S3 credentials may contain characters that are not valid in a URI. That means that the credentials cannot be provided in the URI "basic auth" format, which is the only format Bundler currently supports. As a result, it seems that this feature is broken both in Rubygems and here in Bundler. Attempts to fix the problem have stalled out, and no one on the Bundler core team uses S3 sources, so we've decided to not release support for S3 sources as part of the Bundler gem itself. We're working on a plugin system that will allow S3 support to be implemented and updated without requiring new versions of Bundler to be released. In the meantime, if this support is very important to allow you to continue to work, you can use the the 1.8.0.svn gem as a workaround. : #3345 This reverts commit 1ded21e. This reverts commit b983383. This reverts commit 26214a3. This reverts commit ec0ef95.
We're pulling out svn source support into a plugin. While we work on that, you can use the 1.8.0.svn release, but subversion sources aren't an official part of Bundler itself. This reverts commit 049d281. This reverts commit 22fecdd. This reverts commit 38f195e. This reverts commit 500436a. This reverts commit 2c356be.
Rather than adding .consolerc and seeing the surface area of things that Bundler supports continue to grow endlessly, Bundler 2.0 will deprecate the `bundle console` command, and instead add a script to each generated gem that loads `bundler/setup` and then loads the gem. Anyone can then edit that file to run the REPL they want, load the fixtures they want, and everything else, without anything specific to Bundler at all.