The Pro Client test suite now contains an integration test that covers the scenario described in this bug (Pro client's commands run successfully in a non-utf8 locale).
I have performed the test steps described above for all valid releases, and was able to see the bug is fixed using the package from proposed. There is a problem, as pointed out in #9 and #10 here, when upgrading the package. But that happens when running prerm scripts for the older version of the Client, and debpython expects utf-8 output as well. This means: - this problem when upgrading without utf-8 support may happen to other packages, which use debpython, and - we can't fix it (: Gievn we can now run all Pro Client commands even if a non-utf8 locale is set, I am marking this bug verification-done for all releases. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-noble verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-jammy verification-done-noble verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060769 Title: pro-client decodes utf-8 strictly, which causes problems in some locales To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2060769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
