On May 28, 2009, at 09:10 , Rick DeNatale wrote:
no <package_id> configured for <ri_cal>
$ cat ~/.rubyforge/auto-config.yml
--- [...]
group_ids:
ri-cal: 8408
rical: 8234
package_ids:
ri-cal: 11330
rical: 11041
you've got a registered package of "ri-cal" and "rical" but not
"ri_cal" which is what you configured
$hoe = Hoe.new('ri_cal', RiCal::VERSION) do |p|
p.developer('author=Rick DeNatale', 'rick.denat...@gmail.com')
p.changes = p.paragraphs_of("History.txt",
0..1).join("\n\n")
p.rubyforge_name = 'ri-cal'
p.extra_dev_deps = [
['newgem', ">= #{::Newgem::VERSION}"]
]
p.clean_globs |= %w[**/.DS_Store tmp *.log]
path = (p.rubyforge_name == p.name) ? p.rubyforge_name :
"\#{p.rubyforge_name}/\#{p.name}"
p.remote_rdoc_dir = File.join(path.gsub(/^#{p.rubyforge_name}
\/?/,''), 'rdoc')
p.rsync_args = '-av --delete --ignore-errors'
end
I have no idea what all that crap in there is... I'm going to assume
that is from newgem and ignore it. This should suffice:
Hoe.new('ri_cal', RiCal::VERSION) do |p|
p.rubyforge_name = 'ri-cal'
p.developer('Rick DeNatale', 'rick.denat...@gmail.com')
end
isn't that prettier?
this means: the gem name is "ri_cal" and it is published under the "ri-
cal" rubyforge project. This appears to be the case:
https://rubyforge.org/projects/ri-cal/
has:
https://rubyforge.org/frs/monitor.php?filemodule_id=11330&group_id=8408&start=1
and:
https://rubyforge.org/frs/download.php/57553/ri_cal-0.5.2.gem
I have to admit, I have very few rubyforge projects with "-" in the
name AND discrepancies against the gem name... I've done test-unit but
that had the same name on both. If the above snippet doesn't work,
there is quite possibly a bug somewhere and you'll have to try to
track it down with "ruby -d". I'd start with the rubyforge gem as your
target.
_______________________________________________
Rubygems-developers mailing list
http://rubyforge.org/projects/rubygems
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers
