# How to update gems package version listed by rubygems?

**URL:** <https://www.ruby-forum.com/t/how-to-update-gems-package-version-listed-by-rubygems/50512>\
**Category:** Ruby\
**Created:** [December 17, 2005, 7:38am UTC](https://www.ruby-forum.com/t/how-to-update-gems-package-version-listed-by-rubygems/50512 "2005-12-17T07:38:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kwatch](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/76d3ee/32.png) [@kwatch](https://www.ruby-forum.com/u/kwatch)\
**Post date:** [December 17, 2005, 7:38am UTC](https://www.ruby-forum.com/t/how-to-update-gems-package-version-listed-by-rubygems/50512/1 "2005-12-17T07:38:41Z")

</div>

How to tell rubygems to update gems package version?

I had released my software (named ‘kwalify’) version 0.4.1  
and have just released 0.5.0.  
It is uploaded to RubyForge, but rubygems shows old version.

example: rubygems show old version.  
========================================  
$ gem list --remote kwalify

```
***REMOTE GEMS***
Updating Gem source index for: http://gems.rubyforge.org

kwalify (0.3.0, 0.2.0, 0.1.0)
    a tiny schema validator for YAML document.
========================================

```

Could you tell me how to update latest yaml metadata used by rubygems?

---

<div class="post-metadata">

**Author:** ![kwatch](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/76d3ee/32.png) [@kwatch](https://www.ruby-forum.com/u/kwatch)\
**Post date:** [December 17, 2005, 1:48pm UTC](https://www.ruby-forum.com/t/how-to-update-gems-package-version-listed-by-rubygems/50512/2 "2005-12-17T13:48:00Z")

</div>

On Sat, 17 Dec 2005 06:34:50 -0000, kwatch [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> How to tell rubygems to update gems package version?

I just had a look through your Gem, and it looks to me like you’ve been  
hit with an incompatibility between YAML and Ruby 1.8.3. It was  
discussed  
a bit here recently but I can’t find the thread ☹

If that does sound like you (on Ruby 1.8.3) then you could try the  
following workaround (I have it in my Rakefile):

# Quick fix for Ruby 1.8.3 / YAML bug

if (RUBY\_VERSION == ‘1.8.3’)  
def spec.to\_yaml  
out = super  
out = '— ’ + out unless out =~ /^—/  
out  
end  
end

Hope that helps,  
Ross

---

<div class="post-metadata">

**Author:** ![kwatch](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/76d3ee/32.png) [@kwatch](https://www.ruby-forum.com/u/kwatch)\
**Post date:** [December 17, 2005, 11:04pm UTC](https://www.ruby-forum.com/t/how-to-update-gems-package-version-listed-by-rubygems/50512/3 "2005-12-17T23:04:17Z")

</div>

Thanks Ross, I adopt your workaround and confirmed that  
my \*.gem package is listed by ‘gem list --remote’.

---

<div class="post-metadata">

**Author:** ![kwatch](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/76d3ee/32.png) [@kwatch](https://www.ruby-forum.com/u/kwatch)\
**Post date:** [December 17, 2005, 11:25pm UTC](https://www.ruby-forum.com/t/how-to-update-gems-package-version-listed-by-rubygems/50512/4 "2005-12-17T23:25:28Z")

</div>

On Sat, 17 Dec 2005 22:01:06 -0000, kwatch [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> Thanks Ross, I adopt your workaround and confirmed that  
> my \*.gem package is listed by ‘gem list --remote’.

You’re welcome, but we should really thank the person who posted it  
before, when I was stuck on this same thing 😉  
(As I say, I can’t find it in the archive, but thanks again whoever it  
was).