Gem Recall Notice: win32-api

[Bret Pettichord]

This notice applies to people who installed Watir last week and are
seeing problems.

There was a bad gem, win32-api version 1.3.0 distributed last week. The
problem was fixed with a new gem that was given the same version number.
As a result, the gem installer can't tell whether you have the correct gem.

To fix this problem, you must first uninstall the gem

gem uninstall win32-api -v 1.3.0

Then reinstall the gem

gem install win32-api

We still aren't sure whether other bad windows-gems were released last
week. If the above procedure does not cure your installation, you should
uninstall Ruby and then reinstall all your gems.

Bret

[Bret Pettichord]

Here is a stack trace that indicates that you have the error discussed
below:

C:/ruby/lib/ruby/gems/1.8/gems/win32-api-1.3.0-x86-mswin32-80/lib/win32/api.so:
126: The specified module could not be found. -
C:/ruby/lib/ruby/gems/1.8/gems/win32-api-1.3.0-x86-mswin32-80/lib/win32/api.so
(LoadError)

from
C:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'

from
C:/ruby/lib/ruby/gems/1.8/gems/windows-api-0.3.0/lib/windows/api.rb:1

from
C:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'

from
C:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'

from
C:/ruby/lib/ruby/gems/1.8/gems/windows-pr-1.0.1/lib/windows/error.rb:12

from
C:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'

from
C:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'

from
C:/ruby/lib/ruby/gems/1.8/gems/win32-process-0.6.0/lib/win32/process.rb:1

from
C:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'

from
C:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'

from
C:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.2/lib/watir/ie-process.rb:1

from
C:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'

from
C:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'

from
C:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.2/lib/watir/ie.rb:45

[Bret Pettichord]

For some background on this problem, please see Daniels recent statement.
http://djberg96.livejournal.com/162898.html

[Bret Pettichord]

Magnujf,

You have done all that is necessary in order to repair the specific problem that this notice was written for.

Could you please send a detailed description of what is not working to the Watir General mailing list?

Bret

On Fri, Feb 20, 2009 at 3:26 AM, <mag...@ifi.uio.no> wrote:

Hello, I have tried what you wrote, uninstalling and installing
Ruby.Still not working.
How do I completely uninstall Ruby from windows XP?
Is running the Uninstall-icon inside the Ruby-folder sufficient?
Do I need to install a never wersion than Ruby 1.8 to cope with the
"gems recall" problem? The problem is that the one-click-installer is
version 1.8.6 and that might be the version with the problems "gems
recall". Is there another place to download a one-click-installer
without the "gems recall" problem?

Cheers

On Feb 12, 5:20 pm, Bret Pettichord <b...@pettichord.com> wrote:
> This notice applies to people who installed Watir last week and are
> seeing problems.
>

> There was abadgem, win32-api version 1.3.0 distributed last week. The
> problem was fixed with a newgemthat was given the same version number.
> As a result, thegeminstaller can't tell whether you have the correctgem.

>
> To fix this problem, you must first uninstall thegem
>

>  gemuninstall win32-api -v 1.3.0
>
> Then reinstall thegem
>
>  geminstall win32-api
>
> We still aren't sure whether otherbadwindows-gems were released last

> week. If the above procedure does not cure your installation, you should
> uninstall Ruby and then reinstall all your gems.
>
> Bret

--
Bret Pettichord
GTalk: bpett...@gmail.com
CTO, WatirCraft LLC, http://www.watircraft.com
Lead Developer, Watir, http://www.watir.com
Blog (Essays), http://www.io.com/~wazmo/blog
MiniBlog (Links), http://feeds.feedburner.com/bretshotlist
Training, http://www.watircraft.com/watir-training

[Daniel Berger]

On Feb 13, 10:19 am, Bret Pettichord <b...@pettichord.com> wrote:
> For some background on this problem, please see Daniels recent statement.http://djberg96.livejournal.com/162898.html

To make matters worse, Charley Baker has spotted a problem with Hoe
causing Rubygems to download the wrong precompiled binary:

==
Well, ok. So I've figured out how to reproduce it, seems it's hoe that
actually causing an issue.
- create a basic gemspec
Gem::Specification.new do |s|
....
s.add_dependency 'user-choices' #could be any hoe generated gem
s.add_dependency 'win32-process', '>=0.5.5'
...
end

- build the gem
- install it

When it tries install the win32-api library it grabs the wrong
version. Add the dependency later and it works for this basic example,
but I'm assuming dependencies might not be ordered, since in the
actual Watir gemspec, we have a dependency on common-watir after the
win32 dependency calls; common watir is built with hoe as are some
it's dependencies - user-choices and it's required libs in our case.
==

For now I've decided to go ahead and just delete the mswin32_80 binary
from RubyForge so that the mswin32_60 gem (the one compatible with the
one-click) is the only binary gem posted.

I've posted Charley's email to the rubygems-developers mailing list to
see if anyone knows how exactly Hoe is causing problems.

Sorry for all the trouble folks.

Regards,

Dan

[Charley Baker]

Actually Dan, I'd like to thank you for the work you, Park and others have done on win32-utils and other projects (rubygems) to help make sure that Windows *is* well represented in Ruby. Obviously several of the gems in win32-utils have provided the Watir community with functionality we wouldn't otherwise have and be able to take advantage of.

  So a sincere thanks from me, it's an impressive and helpful amount of work you've provided to both rubyists and watiristas everywhere. Every once in a while there might be hiccups with all the moving parts - in this case it seems to be rubygems and/or hoe - but occasionally that's to be expected.


Charley Baker
blog: http://charleybakersblog.blogspot.com/
Lead Developer, Watir, http://wtr.rubyforge.org
QA Architect, Gap Inc Direct

[Bret Pettichord]

Thanks for the report and for taking this up with the rubygems
developers. I just read your recent posts there, but don't normally
follow that list. Please let me know if involvement will help.

Sincerely,

Bret "top-posting windoze bastard" Pettichord

[Bret Pettichord]

I mean: please let me know if my involvement might help. Again, thanks. Bret