Arjan van de Ven wrote:
On Thu, 2004-06-17 at 17:11, Jeff Spaleta wrote:
I think this is the first time i've seen a package version with a
release number that used non ascii characters. It will be fun to watch
how this sort of thing breaks existing tools
that have been explicitly or implicitly assuming ascii.
yup that's the reason; it's a one off build to see how much of our
infrastructure breaks with utf8 packages.....
Strange. "up2date" works. "up2date -l" does not...
[chris@chris chris]$ up2date -l
Traceback (most recent call last):
File "/usr/sbin/up2date", line 1271, in ?
sys.exit(main() or 0)
File "/usr/sbin/up2date", line 799, in main
fullUpdate, dryRun=options.dry_run))
File "/usr/sbin/up2date", line 1147, in batchRun
batch.run()
File "/usr/share/rhn/up2date_client/up2dateBatch.py", line 62, in run
self.__findPackagesToUpdate()
File "/usr/share/rhn/up2date_client/up2dateBatch.py", line 97, in __findPackagesToUpdate
plist.addGlobs(self.listOfGlobs)
File "/usr/share/rhn/up2date_client/packageList.py", line 157, in addGlobs
availList = rhnPackageInfo.getAvailablePackageList()
File "/usr/share/rhn/up2date_client/rhnPackageInfo.py", line 235, in getAvailablePackageList
ret = up2dateUtils.comparePackages(availPkgsDict[pkgName], pkg)
File "/usr/share/rhn/up2date_client/up2dateUtils.py", line 115, in comparePackages
(epoch2, version2, release2))
UnicodeEncodeError: 'ascii' codec can't encode character u'\u0264' in position 5: ordinal not in range(128)