This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Valid config in 1.6.2 is no longer valid in 1.9.2 #3557
Labels
Comments
punkle
changed the title
Valid config in 1.6.2 is not longer valid in 1.9.2
Valid config in 1.6.2 is no longer valid in 1.9.2
Apr 10, 2015
Ugh, I thought we had fixed this. :( Thanks for the report! |
no probs |
This problem remains in 1.9.4 Environment
|
@punkle @fantasticfears can you provide config example? |
I can't reproduce this anymore after fresh reinstall the RVM. Anyway, my config:
|
@fantasticfears the issue occurs where you use an old config with a later bundler. (I think the trailing slash on the rubygems url is critical to reproducing the issue. not sure) @Strech here is a config example
|
I think, i can fix it 🔧 |
Strech
added a commit
to Strech/bundler
that referenced
this issue
May 14, 2015
Strech
added a commit
to Strech/bundler
that referenced
this issue
May 14, 2015
Strech
added a commit
to Strech/bundler
that referenced
this issue
May 15, 2015
indirect
pushed a commit
that referenced
this issue
May 16, 2015
This should be fixed in the 1.9.9 release, coming out as soon as the CI build passes. |
👍 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I recently updated bunder to version 1.9.2. Config that was valid in the previous version 1.6.2 is no longer valid.
The text was updated successfully, but these errors were encountered: