Sorry my previous post was sent unfinished. Here again and complete: My bad, in my CVS example I had a mistake, here is the correct procedure I used:
$ cd /usr $ cvs -qd anon...@anoncvs.ca.openbsd.org:/cvs get -P ports $ cd /usr/ports/lang/ruby $ cvs up -r OPENBSD_5_8 1.9 But nothing happens I also tried from the same directory this command: $ cvs up -r OPENBSD_5_8 lang/ruby/1.9 Then I just get: cvs [update aborted]: no such directory `lang/ruby' So I am still doing something wrong here but what? Regarding Snorby I patched its config/application.rb for the version checker as suggested, this worked but unfortunately ruby core dumps when I run the "bundle exec rake snorby:setup RAILS_ENV=production". By the way I am using the ruby pacakge 2.0 here from OpenBSD. Regards ML On Saturday, March 19, 2016 9:10 PM, ML mail <mlnos...@yahoo.com> wrote: My bad, in my CVS example I had a mistake, here is the correct procedure I used: $ cd /usr $ cvs -qd anon...@anoncvs.ca.openbsd.org:/cvs get -P ports $ cd /usr/ports/lang/ruby $ cvs up -r OPENBSD_5_8 1.9 But nothing happens I also tried from the same directory this command: $ cvs up -r OPENBSD_5_8 lang/ruby/1.9 Then I just get: On Saturday, March 19, 2016 8:16 PM, Nigel Taylor <njtaylor0...@btinternet.com> wrote: On 03/19/16 17:46, ML mail wrote: > Hi Stuart, > > Thanks for explaining. I now did the following > > $ cd /usr > $ cvs -qd anon...@anoncvs.ca.openbsd.org:/cvs get -P ports > $ cvs up -r OPENBSD_5_8 1.9 > That wasn't what you were instructed to do you have to cd /usr/ports/lang/ruby So you see the 1.8 2.1 sub directories, then your adding 1.9 or from /usr/ports cvs up -r OPENBSD_5_8 lang/ruby/1.9 You said snorby Requirements Snort Ruby >= 1.9.2 Rails >= 3.0.0 Version check fix found on github.... module Snorby # Check Ruby Version - unless RUBY_VERSION.match(/^2.2/) + unless RUBY_VERSION.starts_with?("2.") || RUBY_VERSION.starts_with?("1.9") puts "Snorby requires Ruby version 1.9.x" puts "We suggest using Ruby Version Manager (RVM) https://rvm.io/ to install the newest release" exit 1 My me it used to look for ruby 2.2 only when not found tells you it wants 1.9.x has been changed to look for either 2.x or 1.9.x, still they haven't fixed. So why trying to use 1.9? Only the 3yr old version looks for 1.9, not what's current in github. > > but after running the last command there is simply no output and the 1.9 > directory has not been downloaded from CVS. Am I missing something? Btw I am > running OpenBSD 5.9 (snapshots). > > Regards > ML > > On Saturday, March 19, 2016 10:05 AM, Stuart Henderson <s...@spacehopper.org> > wrote: > On 2016-03-18, ML mail <mlnos...@yahoo.com> wrote: >> You mean I should just take the ports.tar.gz file of OpenBSD 5.8 and compile >> ruby 1.9 from there? >> >> >> I don't really know where is this CVS attic that you mention. > > This is probably the best way (which includes the security fix in -stable): > > $ cd /usr/ports/lang/ruby > $ cvs up -r OPENBSD_5_8 1.9 > U 1.9/Makefile > U 1.9/distinfo > U 1.9/patches/patch-common_mk > U 1.9/patches/patch-compile_c > U 1.9/patches/patch-configure > U 1.9/patches/patch-ext_dl_handle_c > U 1.9/patches/patch-ext_openssl_lib_openssl_ssl-internal_rb > U 1.9/patches/patch-ext_tk_extconf_rb > U 1.9/patches/patch-lib_fileutils_rb > U 1.9/patches/patch-lib_rubygems_commands_install_command_rb > U 1.9/patches/patch-lib_rubygems_dependency_installer_rb > U 1.9/patches/patch-lib_rubygems_ext_builder_rb > U 1.9/patches/patch-lib_rubygems_specification_rb > U 1.9/patches/patch-test_openssl_test_ssl_rb > U 1.9/pkg/DESCR-dbm > U 1.9/pkg/DESCR-gdbm > U 1.9/pkg/DESCR-main > U 1.9/pkg/DESCR-ri_docs > U 1.9/pkg/DESCR-tk > U 1.9/pkg/MESSAGE-main > U 1.9/pkg/PLIST-dbm > U 1.9/pkg/PLIST-gdbm > U 1.9/pkg/PLIST-main > U 1.9/pkg/PLIST-ri_docs > U 1.9/pkg/PLIST-tk > U 1.9/pkg/UNMESSAGE-main