Hello Jaap, or anyone else affected, Accepted libidn into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libidn/1.38-4ubuntu1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libidn (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1971715 Title: 22.04 idn -a domain.com idn: could not convert from ASCII to UTF-8 Status in libidn package in Ubuntu: Fix Released Status in libidn source package in Jammy: Fix Committed Status in libidn source package in Kinetic: Fix Released Bug description: [ Impact ] idn cannot handle non-ASCII characters [ Test Plan ] Existing state in 22.04: $ echo ü | idn idn: could not convert from ASCII to UTF-8 Fixed output: $ echo ü | idn xn--tda [ Where problems could occur ] The patch enables an extra autotools features, so the most likely problem is a build failure. Currently non-ASCII characters are entirely unhandled, so there's no risk of regression there, but this could potentially turn clean failures into crashes or incorrect output. [Original report] On Ubuntu 22.04 Jammy: idn -a "xxx-tést.eu" idn: could not convert from ASCII to UTF-8 And idn -u "xn--xxx-tst-fya.eu" idn: could not convert from UTF-8 to ASCII Expected: Successfully conversion from ASCII to UTF-8 Ubuntu 20.04 / 18.04 it works fine Also with idn2 from UTF-8 to ASCII works as expected how ever support lacks from ASCII to UTF-8 Description: Ubuntu 22.04 LTS Release: 22.04 root@test:~# echo $LC_ALL C.UTF-8 root@test:~# apt-cache policy idn idn: Installed: 1.38-4build1 Candidate: 1.38-4build1 Version table: *** 1.38-4build1 500 500 https://mirror.hetzner.com/ubuntu/packages jammy/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1971715/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
