Bugzilla Bug 157366

all the last ebuilds necessary for nitro+og

Created an attachment (id=103483) [details]
nitro and its companions (og+glue+gen+facets+etc.)

The tar file contains all the ebuilds necessary for nitro

Created an attachment (id=103487) [details]
nitro and its companions (og+glue+gen+facets+etc.)

My mistake... sorry

new tar file with the right versions:
 dev-ruby/cmdparse-2.0.2  
 dev-ruby/facets-1.4.5  
 dev-ruby/glue-0.40.0  
 dev-ruby/og-0.40.0  
 dev-ruby/gen-0.40.0  
 dev-ruby/daemons-0.4.2  
 dev-ruby/ruby-breakpoint-0.5.0  
 dev-ruby/nitro-0.40.0  

it compiles well now

Just checking. You accidentally included facets-1.7.46, didn't you?
What arch have you tested on, x86 and ia64?

(In reply to comment #3)
> Just checking. You accidentally included facets-1.7.46, didn't you?
> What arch have you tested on, x86 and ia64?
> 
Yes indeed. Portage ebuilds doesn't check gem errors very well. So i thought
facets 1.7.46 finally works. In fact portage had just installed empty
directories :(, letting nitro unusable. I checked manually what gem really
wants and not what i would like it should ;). Just ignore it and preferably
stay with the list in comment #2.

I tested it in a amd64 vserver. Some packages need to understand ~amd64. I was
lazy and forced the x86 flag instead. If you prefer, just add the right flag
for your box in the ebuilds. I'm pretty sure if ruby works, nitro and co will
work too ;)

I dropped ~amd64 for og and nitro due to lack of ~amd64 in packages kirbybase,
daemons and redcloth. If you want ~amd64, please file bugs to request arch team
to keyword them.

Your ruby-breakpoint-0.5.1 failed to install with error:

ERROR:  Error installing gem
/mnt/tmp/portage/ruby-breakpoint-0.5.1/distdir/ruby-breakpoint-0.5.1[.gem]:
undefined method `include?' for nil:NilClass

So I'll go with 0.5.0. You can open a new bug for ruby-breakpoint-0.5.1.

Apart from that, your ebuilds have been added in CVS now. Thanks for
contributing.

(In reply to comment #5)
> I dropped ~amd64 for og and nitro due to lack of ~amd64 in packages kirbybase,
> daemons and redcloth. 

Well, you've also dropped ia64 that has all those three stable, please don't do
this...

I'm checking again but I'm pretty sure that the only ia64 I dropped was in
nitro and it was unstable ia64 (bug #157436). I did not touch those three
packages.

(In reply to comment #7)
> I'm checking again but I'm pretty sure that the only ia64 I dropped was in
> nitro and it was unstable ia64 (bug #157436). I did not touch those three
> packages.

Yeah, I meant nitro... OK, didn't notice the other bug, sorry.