{"action":"created","issue":{"url":"https://api.github.com/repos/rubygems/rubygems/issues/1560","repository_url":"https://api.github.com/repos/rubygems/rubygems","labels_url":"https://api.github.com/repos/rubygems/rubygems/issues/1560/labels{/name}","comments_url":"https://api.github.com/repos/rubygems/rubygems/issues/1560/comments","events_url":"https://api.github.com/repos/rubygems/rubygems/issues/1560/events","html_url":"https://github.com/rubygems/rubygems/issues/1560","id":142640266,"number":1560,"title":"Upgrading to rubygems 2.5.x breaks future up/downgrades ('no implicit conversion of nil into String')","user":{"login":"roeme","id":496511,"avatar_url":"https://avatars.githubusercontent.com/u/496511?v=3","gravatar_id":"","url":"https://api.github.com/users/roeme","html_url":"https://github.com/roeme","followers_url":"https://api.github.com/users/roeme/followers","following_url":"https://api.github.com/users/roeme/following{/other_user}","gists_url":"https://api.github.com/users/roeme/gists{/gist_id}","starred_url":"https://api.github.com/users/roeme/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/roeme/subscriptions","organizations_url":"https://api.github.com/users/roeme/orgs","repos_url":"https://api.github.com/users/roeme/repos","events_url":"https://api.github.com/users/roeme/events{/privacy}","received_events_url":"https://api.github.com/users/roeme/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2016-03-22T12:51:22Z","updated_at":"2016-09-07T07:30:54Z","closed_at":"2016-04-12T22:55:37Z","body":"While preparing to upgrade our ruby version, we've found that when updating to a 2.5.x version of rubygems, one can do no more than one additional up-/downgrade - all further up/downgrade attempts fail with `no implicit conversion of nil into String`.\r\n\r\nTo reproduce:\r\n\r\n```\r\n# gem --version\r\n2.0.14\r\ngem update -N --system 2.5.2\r\nUpdating rubygems-update\r\nFetching: rubygems-update-2.5.2.gem (100%)\r\nSuccessfully installed rubygems-update-2.5.2\r\nInstalling RubyGems 2.5.2\r\nRubyGems 2.5.2 installed\r\n\r\n(snip changelog)\r\n\r\nRubyGems installed the following executables:\r\n        /opt/rubies/ruby-2.0.0-p645/bin/gem\r\n\r\nRubyGems system software updated\r\n# gem --version\r\n2.5.2\r\n```\r\n\r\nNow change to another version (2.5.0 shown here, verified with 2.4.8 as well)\r\n\r\n```\r\n# gem update -N --system 2.5.0\r\nUpdating rubygems-update\r\nFetching: rubygems-update-2.5.0.gem (100%)\r\nSuccessfully installed rubygems-update-2.5.0\r\nInstalling RubyGems 2.5.0\r\nRubyGems 2.5.0 installed\r\n\r\nRubyGems installed the following executables:\r\n        /opt/rubies/ruby-2.0.0-p645/bin/gem\r\n\r\nRubyGems system software updated\r\n\r\n# gem --version\r\n2.5.0\r\n\r\n```\r\n\r\nSubsequent attempts fail:\r\n\r\n```\r\n# gem update -N --system 2.5.1\r\nUpdating rubygems-update\r\nFetching: rubygems-update-2.5.1.gem (100%)\r\nERROR:  While executing gem ... (TypeError)\r\n    no implicit conversion of nil into String\r\n# gem update -N --system 2.4.0\r\nUpdating rubygems-update\r\nFetching: rubygems-update-2.4.0.gem (100%)\r\nERROR:  While executing gem ... (TypeError)\r\n    no implicit conversion of nil into String\r\n# gem --version\r\n2.5.0\r\n```\r\n\r\nOne can work around the issue by manually removing the newly installed version within `site_ruby`, downgrading to the version bundled with ruby.\r\n\r\nWe're encountering the issue on both MRI 2.0 and MRI 2.1.\r\n\r\n#1557 is likely related.\r\n\r\n----\r\nThis issue is related to:\r\n- [x] The command line `gem`\r\n\r\nEnvironment details:\r\n- Ruby 2.0\r\n- Ruby 2.1\r\n- CentOS 6.7 \r\n- x86_64\r\n- chruby"},"comment":{"url":"https://api.github.com/repos/rubygems/rubygems/issues/comments/245198719","html_url":"https://github.com/rubygems/rubygems/issues/1560#issuecomment-245198719","issue_url":"https://api.github.com/repos/rubygems/rubygems/issues/1560","id":245198719,"user":{"login":"ujifgc","id":108798,"avatar_url":"https://avatars.githubusercontent.com/u/108798?v=3","gravatar_id":"","url":"https://api.github.com/users/ujifgc","html_url":"https://github.com/ujifgc","followers_url":"https://api.github.com/users/ujifgc/followers","following_url":"https://api.github.com/users/ujifgc/following{/other_user}","gists_url":"https://api.github.com/users/ujifgc/gists{/gist_id}","starred_url":"https://api.github.com/users/ujifgc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ujifgc/subscriptions","organizations_url":"https://api.github.com/users/ujifgc/orgs","repos_url":"https://api.github.com/users/ujifgc/repos","events_url":"https://api.github.com/users/ujifgc/events{/privacy}","received_events_url":"https://api.github.com/users/ujifgc/received_events","type":"User","site_admin":false},"created_at":"2016-09-07T07:30:54Z","updated_at":"2016-09-07T07:30:54Z","body":"On Debian stretch I succeeded to upgrade stock `rubygems` `2.5.1` to `2.6.6` only after running `rm /usr/local/bin/update_rubygems`"}}
{"actor":{"display_login":"ujifgc"}}