NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /var/www/recruiting.gentoo.org/htdocs/vendor/bundle/ruby/1.8/gems/rails-2.3.11/lib/rails/gem_dependency.rb:21. NOTE: Gem::SourceIndex#refresh! is deprecated with no replacement. It will be removed on or after 2011-11-01. Gem::SourceIndex#refresh! called from /var/www/recruiting.gentoo.org/htdocs/vendor/bundle/ruby/1.8/gems/rails-2.3.11/lib/rails/vendor_gem_source_index.rb:34. NOTE: Gem::SourceIndex#load_gems_in is deprecated with no replacement. It will be removed on or after 2011-11-01. Gem::SourceIndex#load_gems_in called from /usr/lib64/ruby/site_ruby/1.8/rubygems/source_index.rb:322. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib64/ruby/site_ruby/1.8/rubygems/source_index.rb:127. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib64/ruby/site_ruby/1.8/rubygems/source_index.rb:127. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib64/ruby/site_ruby/1.8/rubygems/source_index.rb:127. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib64/ruby/site_ruby/1.8/rubygems/source_index.rb:127. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib64/ruby/site_ruby/1.8/rubygems/source_index.rb:127. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib64/ruby/site_ruby/1.8/rubygems/source_index.rb:127. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib64/ruby/site_ruby/1.8/rubygems/source_index.rb:127. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib64/ruby/site_ruby/1.8/rubygems/source_index.rb:127. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib64/ruby/site_ruby/1.8/rubygems/source_index.rb:127. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib64/ruby/site_ruby/1.8/rubygems/source_index.rb:127. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib64/ruby/site_ruby/1.8/rubygems/source_index.rb:127. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib64/ruby/site_ruby/1.8/rubygems/source_index.rb:127. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. .... .... .... we keep getting hundreds of these emails to recruiters@ alias. I guess the webapp should be fixed somehow, but since we have no maintainer could you please hide this warning or just don't send us anything until it is fixed?
I already emailed betelgeuse about it. I see no way to suppress the warning. All that needs to be done is updating the bundled Rails to a newer version.
(In reply to comment #1) > I already emailed betelgeuse about it. > > I see no way to suppress the warning. > > All that needs to be done is updating the bundled Rails to a newer version. Then please shut this application down. Nobody should be using it, nobody maintains it so we should just kill it now.
Agreed, but we need to extract the current answers from the DB then first before killing the webapp
(In reply to comment #3) > Agreed, but we need to extract the current answers from the DB then first > before killing the webapp Why? Stop running the application does not mean erasing the database. Just remove it from the apache on that box. If we need to extract answers we can do that later on. As far as I can tell the application does not offer any export functionality anyway
Yes, I need to do it by hand because I had two mentees that finished the quizes already, and two more that have done a few there
the webapp is now closed. I sent mail to gentoo-core and gentoo-dev-announce (plus I wrote a blog post) to let people know about the termination of the service. As I said in those mails, please inform me about any data you have there and you would like me to export and send to you. Also, infra is willing to revive the service if the recruiters want it back at some point (although personally I'd prefer the UI issues to be resolved first :) )
The resolution of this bug was surprisingly quick. Thanks a lot
Yeah this has also been a problem previously with the cron based solution to running delayed jobs. If we revive the problem hopefully we can use a daemon based approach with infra.
I am still getting the warnings on recruiters@ like I posted on comment #1. Is this really solved? :)
I didn't remove the webapp completely from the server, I just disabled it from apache, thus there was a cronjob still running. It is now disabled. I will remove the webapp from the server completely after I extract the data and keep a final backup of the db
