https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39101 --- Comment #1 from Victor Grousset/tuxayo <victor@tuxayo.net> --- So I guess it can be fixed either by looking at that weird perl behavior. Or by fixing that old DB rev so it actually gets the max_date. Assuming that's correct functionally. A fix might change the code enough to avoid the weird warning. Just reversing the sort with { $b cmp $a } avoids the warning ^^" my ($max_value2) = sort { $b cmp $a } ( $var_with_long_name_1, $var_with_long_name_2, $var_with_long_name_3 ); ---- Should severity be major because it might cause doubt on whether upgrade failed or worked? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.