.
(snip)
.
== 62 InsertBuiltinRoles: migrating ===========================================
DEPRECATION WARNING: The behavior of `changed` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.keys` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
DEPRECATION WARNING: The behavior of `attribute_was` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `attribute_before_last_save` instead. (called from block in position_scope_was at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:57)
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from block in position_scope_was at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:57)
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from block in position_scope_was at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:57)
DEPRECATION WARNING: The behavior of `attribute_was` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `attribute_before_last_save` instead. (called from remove_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:92)
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from remove_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:92)
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from remove_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:92)
DEPRECATION WARNING: The behavior of `changed` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.keys` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
DEPRECATION WARNING: The behavior of `attribute_was` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `attribute_before_last_save` instead. (called from block in position_scope_was at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:57)
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from block in position_scope_was at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:57)
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from block in position_scope_was at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:57)
DEPRECATION WARNING: The behavior of `attribute_was` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `attribute_before_last_save` instead. (called from remove_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:92)
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from remove_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:92)
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from remove_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:92)
== 62 InsertBuiltinRoles: migrated (0.0861s) ==================================
.
(snip)
.
== 20091114105931 AddViewIssuesPermission: migrating ==========================
DEPRECATION WARNING: The behavior of `changed` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.keys` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from update_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:78)
DEPRECATION WARNING: The behavior of `changed` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.keys` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from update_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:78)
== 20091114105931 AddViewIssuesPermission: migrated (0.0245s) =================
.
(snip)
.
== 20170418090031 AddViewNewsToAllExistingRoles: migrating ====================
DEPRECATION WARNING: The behavior of `changed` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.keys` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from update_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:78)
DEPRECATION WARNING: The behavior of `changed` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.keys` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from update_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:78)
== 20170418090031 AddViewNewsToAllExistingRoles: migrated (0.0126s) ===========

== 20170419144536 AddViewMessagesToAllExistingRoles: migrating ================
DEPRECATION WARNING: The behavior of `changed` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.keys` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from update_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:78)
DEPRECATION WARNING: The behavior of `changed` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.keys` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from update_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:78)
== 20170419144536 AddViewMessagesToAllExistingRoles: migrated (0.0112s) =======