win32utils devel - Dec 2007 - [ win32utils-Bugs-16700 ] 1.0.5 x86-mswin32-60 gem is broken

Bugs item #16700, was opened at 2007-12-30 02:04
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=411&aid=16700&group_id=85

Category: win32-api
Group: Packaging
Status: Open
Resolution: None
Priority: 3
Submitted By: Luis Lavena (luislavena)
Assigned to: Nobody (None)
Summary: 1.0.5 x86-mswin32-60 gem is broken

Initial Comment:
Daniel,

The gem you have created with RubyGems 0.9.5 for win32-api is broken, and is
forcing users to the pure-ruby and extension building process instead.

This is part of the specification yaml:

--- !ruby/object:Gem::Specification 
name: win32-api
version: !ruby/object:Gem::Version 
  version: 1.0.5
platform: current
authors: 
- Daniel J. Berger
autorequire: 
bindir: bin
cert_chain: []


platform shouldn''t be current, but i386-mswin32 or x86-mswin32-60.

This problem was fixed in rubygems 1.0, so I suggest you update and recreate the
gem with the correction.

I''m getting a lot of reports of unsuccessful installation of
mongrel_service (which depends on win32-service) due this.

Regards,

Luis

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=411&aid=16700&group_id=85

Bugs item #16700, was opened at 2007-12-29 22:04
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=411&aid=16700&group_id=85

Category: win32-api
Group: Packaging
Status: Open
Resolution: None
Priority: 3
Submitted By: Luis Lavena (luislavena)
Assigned to: Nobody (None)
Summary: 1.0.5 x86-mswin32-60 gem is broken

Initial Comment:
Daniel,

The gem you have created with RubyGems 0.9.5 for win32-api is broken, and is
forcing users to the pure-ruby and extension building process instead.

This is part of the specification yaml:

--- !ruby/object:Gem::Specification 
name: win32-api
version: !ruby/object:Gem::Version 
  version: 1.0.5
platform: current
authors: 
- Daniel J. Berger
autorequire: 
bindir: bin
cert_chain: []


platform shouldn''t be current, but i386-mswin32 or x86-mswin32-60.

This problem was fixed in rubygems 1.0, so I suggest you update and recreate the
gem with the correction.

I''m getting a lot of reports of unsuccessful installation of
mongrel_service (which depends on win32-service) due this.

Regards,

Luis

----------------------------------------------------------------------
>Comment By: Daniel Berger (djberg96)
Date: 2007-12-31 18:50

Message:
Doesn''t CURRENT set it to i386-mswin32-60 if that''s the
compiler it was built with? That''s how the resulting gem name looks.

I''m afraid I do not understand the platform system any more Luis. What
should the gemspec look like?

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=411&aid=16700&group_id=85

Bugs item #16700, was opened at 2007-12-30 02:04
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=411&aid=16700&group_id=85

Category: win32-api
Group: Packaging
Status: Open
Resolution: None
Priority: 3
Submitted By: Luis Lavena (luislavena)
Assigned to: Nobody (None)
Summary: 1.0.5 x86-mswin32-60 gem is broken

Initial Comment:
Daniel,

The gem you have created with RubyGems 0.9.5 for win32-api is broken, and is
forcing users to the pure-ruby and extension building process instead.

This is part of the specification yaml:

--- !ruby/object:Gem::Specification 
name: win32-api
version: !ruby/object:Gem::Version 
  version: 1.0.5
platform: current
authors: 
- Daniel J. Berger
autorequire: 
bindir: bin
cert_chain: []


platform shouldn''t be current, but i386-mswin32 or x86-mswin32-60.

This problem was fixed in rubygems 1.0, so I suggest you update and recreate the
gem with the correction.

I''m getting a lot of reports of unsuccessful installation of
mongrel_service (which depends on win32-service) due this.

Regards,

Luis

----------------------------------------------------------------------
>Comment By: Luis Lavena (luislavena)
Date: 2008-01-01 00:25

Message:
it should look:

platform: x86-mswin32-60

or if was packaged with 0.9.4:

platform: i386-mswin32

The problem is that 0.9.5 was broken and setting platform to
''current'' (actually, current is the text written in the
spec, not Gem::Platform::CURRENT).

So, the resulting gem will be excluded and not properly
picked by rubyforge indexer.

RubyGems 0.9.5 was setting the gem name to -x86-mswin32-60,
but storing into the metadata the wrong information.

RubyGems 1.0.x ships with fixes for this, generating not
just the correct gem name like 0.9.5, but also storing the
proper platform into the metadata.

0.9.5 => Gem::Platform::CURRENT => platform: current (WRONG)
1.0.1 => Gem::Platform::CURRENT => platform: x86-mswin32-60
(GOOD)

Hope this shed some light to the situation.

Regards,

Luis

----------------------------------------------------------------------

Comment By: Daniel Berger (djberg96)
Date: 2007-12-31 22:50

Message:
Doesn''t CURRENT set it to i386-mswin32-60 if that''s the
compiler it was built with? That''s how the resulting gem name looks.

I''m afraid I do not understand the platform system any more Luis. What
should the gemspec look like?

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=411&aid=16700&group_id=85

Bugs item #16700, was opened at 2007-12-29 22:04
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=411&aid=16700&group_id=85

Category: win32-api
Group: Packaging
Status: Open
Resolution: None
Priority: 3
Submitted By: Luis Lavena (luislavena)
Assigned to: Nobody (None)
Summary: 1.0.5 x86-mswin32-60 gem is broken

Initial Comment:
Daniel,

The gem you have created with RubyGems 0.9.5 for win32-api is broken, and is
forcing users to the pure-ruby and extension building process instead.

This is part of the specification yaml:

--- !ruby/object:Gem::Specification 
name: win32-api
version: !ruby/object:Gem::Version 
  version: 1.0.5
platform: current
authors: 
- Daniel J. Berger
autorequire: 
bindir: bin
cert_chain: []


platform shouldn''t be current, but i386-mswin32 or x86-mswin32-60.

This problem was fixed in rubygems 1.0, so I suggest you update and recreate the
gem with the correction.

I''m getting a lot of reports of unsuccessful installation of
mongrel_service (which depends on win32-service) due this.

Regards,

Luis

----------------------------------------------------------------------
>Comment By: Daniel Berger (djberg96)
Date: 2008-01-01 12:06

Message:
Ok, I built and uploaded a new gem for this library. I''ll test it in an
hour or so to make sure it works.

- Dan

----------------------------------------------------------------------

Comment By: Luis Lavena (luislavena)
Date: 2007-12-31 20:25

Message:
it should look:

platform: x86-mswin32-60

or if was packaged with 0.9.4:

platform: i386-mswin32

The problem is that 0.9.5 was broken and setting platform to
''current'' (actually, current is the text written in the
spec, not Gem::Platform::CURRENT).

So, the resulting gem will be excluded and not properly
picked by rubyforge indexer.

RubyGems 0.9.5 was setting the gem name to -x86-mswin32-60,
but storing into the metadata the wrong information.

RubyGems 1.0.x ships with fixes for this, generating not
just the correct gem name like 0.9.5, but also storing the
proper platform into the metadata.

0.9.5 => Gem::Platform::CURRENT => platform: current (WRONG)
1.0.1 => Gem::Platform::CURRENT => platform: x86-mswin32-60
(GOOD)

Hope this shed some light to the situation.

Regards,

Luis

----------------------------------------------------------------------

Comment By: Daniel Berger (djberg96)
Date: 2007-12-31 18:50

Message:
Doesn''t CURRENT set it to i386-mswin32-60 if that''s the
compiler it was built with? That''s how the resulting gem name looks.

I''m afraid I do not understand the platform system any more Luis. What
should the gemspec look like?

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=411&aid=16700&group_id=85

Bugs item #16700, was opened at 2007-12-29 22:04
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=411&aid=16700&group_id=85

Category: win32-api
Group: Packaging
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Luis Lavena (luislavena)
>Assigned to: Daniel Berger (djberg96)
Summary: 1.0.5 x86-mswin32-60 gem is broken

Initial Comment:
Daniel,

The gem you have created with RubyGems 0.9.5 for win32-api is broken, and is
forcing users to the pure-ruby and extension building process instead.

This is part of the specification yaml:

--- !ruby/object:Gem::Specification 
name: win32-api
version: !ruby/object:Gem::Version 
  version: 1.0.5
platform: current
authors: 
- Daniel J. Berger
autorequire: 
bindir: bin
cert_chain: []


platform shouldn''t be current, but i386-mswin32 or x86-mswin32-60.

This problem was fixed in rubygems 1.0, so I suggest you update and recreate the
gem with the correction.

I''m getting a lot of reports of unsuccessful installation of
mongrel_service (which depends on win32-service) due this.

Regards,

Luis

----------------------------------------------------------------------
>Comment By: Daniel Berger (djberg96)
Date: 2008-01-01 15:01

Message:
Looks like it''s fixed. I did a remote install and it did not attempt to
build from source, so that''s good.

Please reopen if I messed up again.

Thanks,

Dan

----------------------------------------------------------------------

Comment By: Daniel Berger (djberg96)
Date: 2008-01-01 12:06

Message:
Ok, I built and uploaded a new gem for this library. I''ll test it in an
hour or so to make sure it works.

- Dan

----------------------------------------------------------------------

Comment By: Luis Lavena (luislavena)
Date: 2007-12-31 20:25

Message:
it should look:

platform: x86-mswin32-60

or if was packaged with 0.9.4:

platform: i386-mswin32

The problem is that 0.9.5 was broken and setting platform to
''current'' (actually, current is the text written in the
spec, not Gem::Platform::CURRENT).

So, the resulting gem will be excluded and not properly
picked by rubyforge indexer.

RubyGems 0.9.5 was setting the gem name to -x86-mswin32-60,
but storing into the metadata the wrong information.

RubyGems 1.0.x ships with fixes for this, generating not
just the correct gem name like 0.9.5, but also storing the
proper platform into the metadata.

0.9.5 => Gem::Platform::CURRENT => platform: current (WRONG)
1.0.1 => Gem::Platform::CURRENT => platform: x86-mswin32-60
(GOOD)

Hope this shed some light to the situation.

Regards,

Luis

----------------------------------------------------------------------

Comment By: Daniel Berger (djberg96)
Date: 2007-12-31 18:50

Message:
Doesn''t CURRENT set it to i386-mswin32-60 if that''s the
compiler it was built with? That''s how the resulting gem name looks.

I''m afraid I do not understand the platform system any more Luis. What
should the gemspec look like?

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=411&aid=16700&group_id=85