| Summary: | dev-ruby/rubigen fails tests | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
| Component: | New packages | Assignee: | Gentoo Ruby Team <ruby> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://github.com/drnic/rubigen/issues/issue/2 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Build log
/var/tmp/portage/dev-ruby/rubigen-1.5.7/temp/build.log |
||
|
Description
Diego Elio Pettenò (RETIRED)
2010-05-20 20:39:36 UTC
Created attachment 232273 [details]
Build log
This only happens when rubigen is not yet installed, so there is a problem with finding the generators in the source tree. I've filed an upstream bug about it. The ebuild now depends on itself for tests which avoids this error. Leaving the bug open since this should be resolved properly. Created attachment 301363 [details]
/var/tmp/portage/dev-ruby/rubigen-1.5.7/temp/build.log
Build.log with failures when rubigen is already installed
(In reply to comment #3) > The ebuild now depends on itself for tests which avoids this error. Leaving the > bug open since this should be resolved properly. As the description of my attachment indicates, I can reproduce failures even if rubigen is installed (even if rubigen is installed with USE="test" by using FEATURES="test-fail-continue") It looks like this happen because x86 only has a very old version of cucumber keyworded. We should prepare a keywording bug for that first, then. dev-ruby/rubigen is now removed from the tree. |