close 954165 2.0.3-3.1 thanks Hi,
although this bug is still present when upgrading from deluge 1.x to
2.x, it doesn't make sense to keep the bug report open here:
* doing a debian specific patch enforcing non-utf8 charset doesn't
make sense for the future (also because everyone else already has
fixed/deleted their state files since)
* the upgrade now would be applicable when upgrading from buster to
bullseye, but not for any upgrades afterwards.
Regards,
Daniel
