Downloads of v 2.4.6:


Last Update:

24 Feb 2015

Package Maintainer(s):

Software Author(s):

  • Nick Quaranto


rubygems ruby




Downloads of v 2.4.6:



Software Author(s):

  • Nick Quaranto


rubygems ruby

  • 1
  • 2
  • 3

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Failed


Scan Testing Unknown

This package was rejected on 18 Jan 2016. The reviewer carolynvs has listed the following reason(s):

anthonymastrean (reviewer) on 15 April 2015:


This package seems a bit complicated now. I might not understand some nuance of the setup, but here are some of my observations...

  • The try...catch and Write-ChocolateySuccess/Failure are built-in and unnecessary in the scripts now.
  • The Set-Location and $pwd stashing can be replaced with Push- and Pop-Location (I guess you might want a try...finally around this still).
  • The Get-ChocolateyWebFile and Get-ChocolateyUnzip combo can be replaced with just Install-ChocolateyZipPackage.

I whipped up this edition and tested it quickly on my local machine. Let me know if it works for you.

$id = 'rubygems'
$url = ''

$tools = Split-Path $MyInvocation.MyCommand.Definition
$zip = Join-Path $tools 'rubygems-2.4.6'

Install-ChocolateyZipPackage -PackageName $id -Url $url -UnzipLocation $tools

try {
Push-Location $zip
Start-ChocolateyProcessAsAdmin -Statements 'setup.rb' -ExeToRun 'ruby'
} finally {

I feel a little pushy giving this much feedback, but I think a simpler script will lead to faster moderation. Thanks for your patience :)

~ Anthony

chocolatey-ops (reviewer) on 02 Dec 2015 03:56:18 +00:00:

rubygems has failed testing.
Please visit for details.
The package status will be changed and will be waiting on your next actions.

ferventcoder (reviewer) on 14 Dec 2015 20:24:40 +00:00:

Ping, what needs to change here?

chocolatey-ops (reviewer) on 20 Dec 2015 10:54:54 +00:00:

rubygems has passed automated validation.
NOTICE: We are permanently fixing our backlog issues and we want to apologize that it has taken so long - please see

NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.


Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • This package uses a helper function that requires administrative permissions, the tag 'admin' should also be in the nuspec. More...
    • NOTE: This becomes a Requirement starting on 1 February 2016.
  • Package contains dependencies with no specified version. You should at least specify a minimum version of a dependency. More...
  • The nuspec has been enhanced to allow packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Write-ChocolateySuccess/Write-ChocolateyFailure have been deprecated, but have been found in the package's automation scripts. Remove the usage of those two functions. If there is an error, throw the error. More... This can also give a false positive for commented code with the words:
    • Write-ChocolateySuccess
    • Write-ChocolateyFailure
  • Title (title) matches id exactly. Please consider using something slightly more descriptive for the title in the nuspec. More...

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
    • docsUrl - points to the location of the wiki or docs of the software
    • mailingListUrl - points to the forum or email list group for the software
    • bugTrackerUrl - points to the location where issues and tickets can be accessed
    • projectSourceUrl - points to the location of the underlying software source

chocolatey-ops (reviewer) on 15 Jan 2016 01:26:47 +00:00:

We've found rubygems v2.4.6 in a submitted status and waiting for your next actions. It has had no updates within 20 days after a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

  • Log in to the site and respond to the review comments.
  • Resubmit fixes for this version.
  • If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

carolynvs (maintainer) on 18 Jan 2016 21:17:55 +00:00:

Now that ruby 1.9 is no longer supported, the reasons for having a separate package for rubygems are gone.
Status Change - Changed status of package from 'submitted' to 'rejected'.


The Ruby community's gem hosting service.

$pwd = Get-Location
$packageName = 'rubygems'
$version = '2.4.6'
$zipName = "rubygems-$"
$url = "$zipName"
$validExitCodes = @(0)
$scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$zipPath = Join-Path $scriptPath $zipName
$setupDir = Join-Path $scriptPath "rubygems-$version"

try {

  Get-ChocolateyWebFile "$packageName" "$zipPath" "$url"
  Get-ChocolateyUnzip "$zipPath" "$scriptPath"
  Set-Location $setupDir
  Start-ChocolateyProcessAsAdmin 'setup.rb' 'ruby' -validExitCodes $validExitCodes

  Write-ChocolateySuccess "$packageName"
} catch {
  Write-ChocolateyFailure "$packageName" "$($_.Exception.Message)"
finally {
  Set-Location $pwd

No results available for this package. We are building up results for older packages over time so expect to see results. If this is a new package, it should have results within a day or two.

Version Downloads Last Updated Status
Discussion for the RubyGems Package

Ground Rules:

  • This discussion is only about RubyGems and the RubyGems package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or RubyGems, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus