On 24/06/2023 02.22, Georg Faerber wrote:
I believe that's caused by ruby-arel, the attached patches fix the issue
in my tests.
Shouldn't these conflicts rather be in ruby-activerecord?
As I understand the history, arel has been merged into activerecord (5
years ago, probably version 6.0.x) and the "old" arel 9 is no longer
compatible with current activerecord 6.1.x. This is probably unrelated
to schleuder (which only exposes the bug).
Interestingly this didn't happen on buster->bullseye upgrades, but
perhaps arel 9 was still compatible with activerecord 6.0.x.
Should ruby-arel be RM:ed?
Note: one reverse build dependency
# Broken Build-Depends:
ruby-premailer-rails: ruby-arel
Andreas, are you able to test these in your environment?
I'll give it a try... yes, the conflict against ruby-arel fixes the
upgrade path.
Andreas,
who has no clue at all about ruby
