2011/9/6 Antonio Terceiro <[email protected]>: > Usually we also want to remove insane manipulations of the $LOAD_PATH, > such as: > > $:.unshift "../../ruby_parser/dev/lib" > $:.unshift "../../ruby2ruby/dev/lib" > > ($: == $LOAD_PATH) > > I updated your patch, check 1db9635. Please ping me again when > ruby-sexp-processor hits the archive. It was already accepted, so this should > be really soon now.
It is in the archive now, I updated the patch for dep3. > -------------------------------------------------------------------- > > re ruby-cutest: > > debian/patches/remove-hard-coded-lib-path.patch: `require 'cutest'` > should Just Work, since lib/cutest.rb will end up in the $LOAD_PATH. changed. > debian/control: short description must not begin with package name updated. > debian/ruby-tests.rb is all commented out, but there are tests in the > package to be run during the build. I updated it, but I think I will need help with this. It is using its own syntax (cutest syntax) and I followed its README. But one test is failing. But it doesn't appear as failure to our test_runner. error output is /usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb .................. Cutest::AssertionFailed: "\n" != ".\n" - assert_equal(stdout, expected) ./test/run.rb +20 /usr/bin/ruby1.9.1 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb .................. Cutest::AssertionFailed: "\n" != ".\n" - assert_equal(stdout, expected) ./test/run.rb +20 Any ideas? -- പ്രവീണ് അരിമ്പ്രത്തൊടിയില് You have to keep reminding your government that you don't get your rights from them; you give them permission to rule, only so long as they follow the rules: laws and constitution. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/caoo+evqs+kg+1odcdyj4yaizslu15c9blz0l_zpda7xx-pd...@mail.gmail.com
