It happened to me today as well. As the referenced question says: it happens if you upload the same version of source package for the second time && there is an accented character in the maintainer name. I bumped version number in changelog and launchpad accepted that upload without any other change.
I think it has to do with some internal package metadata storage inside soyuz (which is in ascii), since the package doesn't influence that by itself.
For your information, I got this exact message:
Unhandled exception processing upload: 'ascii' codec can't encode character u'\xe1' in position 57: ordinal not in range(128)
[...]
Maintainer: Václav Šmilauer
Related question mentioning workaround: https:/ /answers. launchpad. net/launchpad/ +question/ 45857
It happened to me today as well. As the referenced question says: it happens if you upload the same version of source package for the second time && there is an accented character in the maintainer name. I bumped version number in changelog and launchpad accepted that upload without any other change.
I think it has to do with some internal package metadata storage inside soyuz (which is in ascii), since the package doesn't influence that by itself.
For your information, I got this exact message:
Unhandled exception processing upload: 'ascii' codec can't encode character u'\xe1' in position 57: ordinal not in range(128)
[...]
Maintainer: Václav Šmilauer
\xe1 is "á"