help: no <processor_id> configured for <Any> error ?

3 views
Skip to first unread message

mortench

unread,
Apr 14, 2008, 10:17:16 AM4/14/08
to New Gem Generator
I am trying to release my first public gem "railscheck" on rubyforge
using newgem and have success right up until deployment of the gem
itself where get this strange error:

no <processor_id> configured for <Any>
/Library/Ruby/Gems/1.8/gems/rubyforge-0.4.5/lib/rubyforge.rb:389:in
`lookup'
/Library/Ruby/Gems/1.8/gems/rubyforge-0.4.5/lib/rubyforge.rb:256:in
`add_release'
/Library/Ruby/Gems/1.8/gems/hoe-1.5.1/lib/hoe.rb:546:in `define_tasks'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:544:in `call'

Everthing else like uploading site documentation and rdoc works but
not uploading the gem itself

Any idea what I can do ?

I have tried googling and looking at hoe documentation to no avail.
The bug seems to be related to specifying the CPU processor for the
uploaded package which makes no sense in my case.

P.S. I also made a smaller comment on another thread but the title is
misleading so hence a new topic for this error

Thanks in advance,
Morten

Nic Williams

unread,
Apr 14, 2008, 10:31:09 AM4/14/08
to new-gem-...@googlegroups.com
Can you also post this question to hoe's forum? Eric+Ryan might know something about this.


I'll try to recreate the problem by clearing out my .rubyforge + .hoerc files and see if I can see what everyone else is getting.

But, try reading the http://newgem.rubyforge.org/rubyforge.html docco. Might be something there, not sure.

Nic
--
Dr Nic Williams
http://drnicacademy.com - Ruby/Rails training/dev around the world
http://drnicwilliams.com - Ruby/Rails/Javascript/Web2.0
(skype) nicwilliams
(p) +61 412 002 126 / +61 7 3113 3033
(mail) PO Box 583 Ashgrove 4060 QLD Aus

mortench

unread,
Apr 14, 2008, 11:30:06 AM4/14/08
to New Gem Generator
Thanks for looking into this.

I posted a report (#19515) on the hoe forum you linked to.

An idea: You mentioned that you recently added support for native
extensions. Could this bug have
something to do with that as native extensions might require cpu
processor to be specified? ..Nb. I have
no native code in my ruby-only gem.

Cheers,
Morten

On Apr 14, 4:31 pm, "Nic Williams" <drnicwilli...@gmail.com> wrote:
> Can you also post this question to hoe's forum? Eric+Ryan might know
> something about this.
> Tryhttp://rubyforge.org/tracker/?atid=5921&group_id=1513&func=browse
>
> I'll try to recreate the problem by clearing out my .rubyforge + .hoerc
> files and see if I can see what everyone else is getting.
>
> But, try reading thehttp://newgem.rubyforge.org/rubyforge.htmldocco. Might
> be something there, not sure.
>
> Nic
>
>
>
> On Tue, Apr 15, 2008 at 12:17 AM, mortench <morte...@gmail.com> wrote:
>
> > I am trying to release my first public gem "railscheck" on rubyforge
> > using newgem and have success right up until deployment of the gem
> > itself where get this strange error:
>
> > no <processor_id> configured for <Any>
> > /Library/Ruby/Gems/1.8/gems/rubyforge-0.4.5/lib/rubyforge.rb:389:in
> > `lookup'
> > /Library/Ruby/Gems/1.8/gems/rubyforge-0.4.5/lib/rubyforge.rb:256:in
> > `add_release'
> > /Library/Ruby/Gems/1.8/gems/hoe-1.5.1/lib/hoe.rb:546:in `define_tasks'
> > /Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:544:in `call'
>
> > Everthing else like uploading site documentation and rdoc works but
> > not uploading the gem itself
>
> > Any idea what I can do ?
>
> > I have tried googling and looking at hoe documentation to no avail.
> > The bug seems to be related to specifying the CPU processor for the
> > uploaded package which makes no sense in my case.
>
> > P.S. I also made a smaller comment on another thread but the title is
> > misleading so hence a new topic for this error
>
> > Thanks in advance,
> > Morten
>
> --
> Dr Nic Williamshttp://drnicacademy.com- Ruby/Rails training/dev around the worldhttp://drnicwilliams.com- Ruby/Rails/Javascript/Web2.0

Nic Williams

unread,
Apr 15, 2008, 12:33:58 AM4/15/08
to new-gem-...@googlegroups.com
So you are using the ext_conf generator when you are having this problem?

I just created a new gem (foo - who'd have thought there were no foo gems yet) and uploaded it. I've also included copies of my various config files. Let me know if you find anything different in your config files.

--
Dr Nic Williams
http://drnicacademy.com - Ruby/Rails training/dev around the world
http://drnicwilliams.com - Ruby/Rails/Javascript/Web2.0

mortench

unread,
Apr 15, 2008, 3:43:47 AM4/15/08
to New Gem Generator
Hi Nic,

Thanks for the list of your config files. That helped me find the
problem.

My auto-config.yml did not contain any processor_ids so I copied yours
to my file and it works now (I also did not have any ~/.hoerc file but
that seems not to be a problem).

I am now waiting to see if my gem shows up in the gem repository
automatically (crossing my fingers since I don't quite understand the
exact process of how/when rubyforge file uploads and the gem command
work together. Anyone care to explain ?).

P.S. I was using your standard recipe at "http://
newgem.rubyforge.org/" + "http://newgem.rubyforge.org/rubyforge.html"
(and not using ext_conf).


Thanks,
Morten

Nic Williams

unread,
Apr 15, 2008, 3:48:25 AM4/15/08
to new-gem-...@googlegroups.com
You can see if it was successful by going to the project page on rubyforge. I'm told the mirroring happens within an hour.
--
Dr Nic Williams
http://drnicacademy.com - Ruby/Rails training/dev around the world
http://drnicwilliams.com - Ruby/Rails/Javascript/Web2.0

mortench

unread,
Apr 15, 2008, 9:56:11 AM4/15/08
to New Gem Generator
Hi Nic,

Yes, all is well. The upload worked!

Thanks to newgem and you Nic, my first publicly released rubygem
"railscheck" (a semi-static Q/A verification tool for Ruby on Rails)
is now successfully released in version 0.1.1 on
"railscheck.rubyforge.org".

Newgem is a great tool. Saved me a lot of work.

/Cheers,
Morten

rogerdpack

unread,
May 30, 2008, 10:42:21 PM5/30/08
to New Gem Generator
> My auto-config.yml did not contain any processor_ids so I copied yours
> to my file and it works now (I also did not have any ~/.hoerc file but
> that seems not to be a problem).

yep. same problem, same resolution.
Thanks for finding that!
no idea why
rubyforge setup
and
rubyforge config
didn't set that up right. Oh well.
Should be able to checkout my latest gem 'doctest' any time :)
-R
Reply all
Reply to author
Forward
0 new messages