---
Must also rename Zulassunginhaber -> Zulassungs-I.
But first remarked that jobs/import_medreg_companies did not correctly create the companies. Their name and ean13 were not updated correctly. Trying a workaround. Found now the correct way on how to update the companies, but the business_area is still wrong.
Changed all hc_provider => pharmacy. Unit-Tests works, but searching does not yet work. See
Watir tests must check the following points
Added watir tests for http://oddb-ci2.dyndns.org/de/gcc/doctor/ean/7601000254207. Dr. Züst in Mollis. See commit Added watir test for doctors
No fax present yet.
Asking myself again how to get a working mod_ruby on my oddb-ci2. Funtoo portage is great if you have a checkout that fulfills your requirements, but when doing my installation last year I did not bother to write the portage git hash down and I am afraid to switch to a portage tag of last year.
Trying whether ist works with apache 2.2.15 (as specified under https://github.com/zdavatz/oddb.org/blob/master/Guide.txt), with ruby18 and mod_ruby 1.3.0. Running as root
eselect ruby set ruby18 grep RUBY /etc/conf.d/apache2 > APACHE2_OPTS="-D RUBY -D DEFAULT_VHOST -D INFO -D SSL -D SSL_DEFAULT_VHOST -D LANGUAGE" emerge =apache-2.2.26 # was 2.2.15 is no longer available =mod_ruby-1.3.0 # getting rid of some ruby 2.0 packages emerge --unmerge dev-lang/ruby-2.0.0_p353-r2 emerge --unmerge dev-ruby/racc-1.4.1 dev-ruby/rdoc-4.0.1-r2 dev-ruby/json-1.8.1 dev-ruby/rake-0.9.6-r1 oddb-ci2 niklaus # emerge rubygems * IMPORTANT: config file '/etc/portage/package.license' needs updating. * See the CONFIGURATION FILES section of the emerge * man page to learn how to update config files. Calculating dependencies... done! [ebuild NS ] dev-lang/ruby-2.1.0 [1.8.7_p374-r1, 1.9.3_p545] USE="berkdb gdbm ipv6 ncurses rdoc readline ssl -debug -doc -examples -rubytests -socks5 -tk -xemacs" [ebuild R ] dev-ruby/rubygems-2.0.14 RUBY_TARGETS="ruby21* -ruby20*" [ebuild NS ] virtual/rubygems-7 [1, 4] RUBY_TARGETS="(ruby21)" [ebuild N ] dev-ruby/rake-0.9.6-r1 USE="-doc {-test}" RUBY_TARGETS="ruby18 ruby19 ruby21 -jruby -ruby20" [ebuild N ] dev-ruby/json-1.8.1 USE="-doc {-test}" RUBY_TARGETS="ruby18 ruby19 ruby21 -jruby -ruby20" [ebuild N ] dev-ruby/racc-1.4.11 USE="-doc {-test}" RUBY_TARGETS="ruby18 ruby19 ruby21 -jruby -ruby20" [ebuild N ] dev-ruby/rdoc-4.0.1-r2 USE="-doc {-test}" RUBY_TARGETS="ruby18 ruby19 ruby21 -jruby -ruby20"
Continued to get same error even after creating /etc/portage/package.use/ruby
with =dev-lang/ruby-2.1.0 berkdb gdbm ipv6 ncurses rdoc readline ssl -debug -doc -examples -rubytests -socks5 -tk -xemacs
After diging around, and looking at /etc/conf.d/._cfg0005_apache2 I see that mod_ruby does not seem to be valid. Googling aroun found that http://www.gossamer-threads.com/lists/gentoo/dev/285557 mod_ruby was slated for removal in 30 days on Mar 22, 2014, 12:17 AM. I don't know how to resolve this problem.
mod_ruby has been removed from Debian, too. See https://packages.qa.debian.org/m/mod-ruby.html
But im portage (commit 8030f2b37512a03af3c07777b2f2c469d745d053) from Sat Mar 1 01:03:34 2014 -0700
mod_ruby is still there. So why does it not work?
After re-adding ruby21 to RUBY_TARGETS in /etc/portage/make.conf, running emerge dev-lang/ruby
and applying again the csv.rb patch http://dev.ywesee.com/uploads/att/csv.rb.patch.20111123.txt. Also hat to patch sbsm.rb as shown in http://dev.ywesee.com/Niklaus/20140225-add-medical-products-3#DRBunknown.
Now oddb-ci2 comes up again.