Please mark dev-ruby/markaby-0.7.1 and its dependency stable. This version has been in the tree for >6 months and has no open bugs. =dev-ruby/tilt-1.2.2 =dev-ruby/markaby-0.7.1
amd64: =dev-ruby/tilt-1.2.2 emerged and passes test. =dev-ruby/markaby-0.7.1 emerged with test unset. prior version passed the test. * Running test phase for ruby18 ... (in /mnt/gen2/tmpdir/portage/dev-ruby/markaby-0.7.1/work/ruby18/markaby-0.7.1) Could not load hanna-rdoc. Please install with mislav-hanna package Jeweler not available. Install it with: sudo gem install technicalpickles-jeweler -s http://gems.github.com dev-ruby/rspec-1.3.1 emerged ok.
https://bugs.gentoo.org/show_bug.cgi?id=343693 already in place, matches this version.
Removing arches until the test failures are fixed.
This stabilization should now be good to go again.
I am still getting the same test failures in amd64
I can not reproduce any emerge failures on amd64.
(In reply to comment #6) > I can not reproduce any emerge failures on amd64. The failures depend on the order in which specs are run and this varies from system to system (I expect due to differences in file systems). @Markos: I've changed the patch to always load the missing 'require' before any specs, so things should work for you now.
amd64: have tried and tried; make some headway but still fails test. Skipping rails specific tests /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in \ `gem_original_require': no such file to load Seems to be missing suppport files.
(In reply to comment #8) > amd64: > have tried and tried; make some headway but still fails test. > > Skipping rails specific tests > /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in \ > `gem_original_require': no such file to load > > Seems to be missing suppport files. If these tests still fail for you with current CVS then please attach a build log.
done. https://bugs.gentoo.org/attachment.cgi?id=287293
No response to our AT, please address the matter described and re-add us to CC. To confirm, no 30 day limits apply here.
(In reply to comment #11) > No response to our AT, please address the matter described and re-add us to CC. > To confirm, no 30 day limits apply here. That build log predates my fix by a month so I don't really see how that is relevant. Readding amd64.
@graaff: The following keyword changes are necessary to proceed: #required by dev-ruby/markaby-0.7.1[test,ruby_targets_ree18], required by =dev-ruby/markaby-0.7.1 (argument) >=dev-ruby/tilt-1.3.2 ~amd64 Ok to stabilize also tilt?
(In reply to comment #13) > Ok to stabilize also tilt? I didn't explain better, so, as per comment #0 there is an "ok" to stabilize tilt, but there, is specified 1.2.2, now is required 1.3.2. Anyway there is a test failure for tilt, and I guess that blocks this stabilization.
(In reply to comment #14) > I didn't explain better, so, as per comment #0 there is an "ok" to stabilize > tilt, but there, is specified 1.2.2, now is required 1.3.2. > Anyway there is a test failure for tilt, and I guess that blocks this > stabilization. markaby's tests are not compatible with newer versions of tilt, so 1.2.2 should be stabilized. I don't see how tilt 1.3.2 is required?
Actually with all the delays with this bug I think we should try a better plan. Let's just stabilize the latest versions since these have been in the tree for some time now also. =dev-ruby/tilt-1.3.2 =dev-ruby/markaby-0.7.2
(In reply to comment #16) > =dev-ruby/tilt-1.3.2 > =dev-ruby/markaby-0.7.2 both ok now.
amd64 done. Thanks Agostino
dropped stable keywords back to ~ppc64