This is a generic keyword bug. Fxruby has been neglected quite a bit, while i messed with other stuff. So please give it some love :) Ideally, i would ask every arch but hppa for stable keywords on: fxruby-1.2.6 fxruby-1.4.7 fxruby-1.6.4 I would like to hppa to keyword the above ebuilds ~hppa or drop out of fxruby completly. That's needed for fxscintilla (bug #108628), that's why i'm pressing this now. Apologies to the ruby herd if i stepped on their toes, feel free to override me.
All three marked ~hppa.
fxruby stable on x86, fxscintilla has been handled too.
amd64 stable
Sparc can't use fxscintilla-1.71 with fxruby-1.2.6: bus error at exit; -1.62-r2 is OK for fox12, but fxruby-1.2.6 won't build against it because the library it installs is not libfxscintilla.so. fxruby-1.4.7 appears to be completely bad --- Bug 175207 fxruby-1.6.4+fxscintilla-1.71 appears to be a winning combination, but we can't unmask & stable fxscintilla-1.71 because fxruby-1.2.6 cannot use it without aborting. (fxruby-1.6.11+fxscintilla-1.71 is good for that matter.) Sparc can't do anyting here until the -1.4.7 issue and the -1.2.6+fxscintilla-1.71 issue are resolved, so I'm removing sparc from the CC for now.
How about punting all -1.2* ebuilds (which will include fxscintilla not building against fox-1.2 anymore), killing the ~sparc on fxruby-1.4 and go for fxruby-1.6*? Would that help you? IMHO that would solve your problems. I intend to remove the fox-1.2 dep stuff in the upcoming months anyway, so let's move forward with it.
(In reply to comment #6) > How about punting all -1.2* ebuilds (which will include fxscintilla not > building against fox-1.2 anymore), killing the ~sparc on fxruby-1.4 and go for > fxruby-1.6*? > Would that help you? IMHO that would solve your problems. > As best as I can tell, yes it would. If possible, please tie it to a request for -1.6.11 to go stable (that's due in a little over a week anyway.) > I intend to remove the fox-1.2 dep stuff in the upcoming months anyway, so > let's move forward with it. >
Time to handle it. Sparc needs to mask fxruby-1.2 at the same time. The ebuilds will disappear shortly after sparc and alpha have marked newer versions stable. All others: please give fxruby-1.6.11 some love. I guess a working freeride is enough of a testcase :)
1.6.11 stable on ppc. 1.4 shows the same behaviour as in bug #175207 and will be either removed or fixed (former is more likely since upstream has no current access to arches where this fails and the release is outdated anyway).
Alpha done.
Created attachment 119863 [details] freeride-0.9.6, both stdout and stderr dev-util/freeride-0.9.6 doesn't seem to want to start at all. After the last message, the process hangs. A break adds just this: /usr/lib/ruby/site_ruby/freeride/freebase/lib/freebase/core.rb:37:in `sleep': Interrupt from /usr/lib/ruby/site_ruby/freeride/freebase/lib/freebase/core.rb:37:in `startup' from /usr/lib/ruby/site_ruby/freeride/freeride.rb:77:in `startup' from /usr/lib/ruby/site_ruby/freeride/freeride.rb:116 Any idea what causes this?
(In reply to comment #8) > Time to handle it. Sparc needs to mask fxruby-1.2 at the same time. The ebuilds > will disappear shortly after sparc and alpha have marked newer versions stable. > > All others: please give fxruby-1.6.11 some love. I guess a working freeride is > enough of a testcase :) > Where would a current freeride by? Latest I can find is -0.9.6, which seems to depend on fox12. If I force it to use fox16, I see the hang in sleep as mentioned in Comment 11. That said, -1.6.11 is stable on sparc, and -1.2.x is package.masked on sparc.
Stable for HPPA. Some of the examples work fine, others seem to depend on gems that aren't installed. Also note that the examples' README should probably not be executable: -rwxr-xr-x 1 root root 1907 2007-05-21 05:44 /usr/share/doc/fxruby-1.6.11/examples/README
x86/amd64 stable
ppc64 stable last arch CC'd -> marking bug as FIXED
