search

rikho / munki

Automatically exported from code.google.com/p/munki
Other
0 stars 0 forks source link

Munki 2 - UTF encoding display_name error #299

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 

What steps will reproduce the problem?
1. Import MS Silverlight with the defaults 
2. The pkginfo display_name will be <string>Microsoft® Silverlight™ Browser 
Plug-In</string>
3. Assign it to the client's manifest and open Munki2 in the client

What is the expected output? What do you see instead?
Any window that includes Silverlight will not render. The display_name encoding 
gives an error and the .html files are not created

What version of the Munki tools/InstallOSpkg tools are you using? On what
version of OS X?
Munki 2.0.0.1944
OS X 10.9.2

Please provide any additional information below.
I've gone thought MunkiItems.py trying to fix this but my python skills aren't 
good enough

log attached

Original issue reported on code.google.com by nbalonso on 23 Mar 2014 at 12:31

Attachments:

GoogleCodeExporter commented 9 years ago 
Last night while playing with html descriptions, I ran into some UTF errors.

I cannot reproduce your issue though. Could you post your pkginfo?

Original comment by eriknico...@gmail.com on 23 Mar 2014 at 9:17

GoogleCodeExporter commented 9 years ago 
I can reproduce it. Fix forthcoming.

Original comment by gregnea...@mac.com on 24 Mar 2014 at 12:45

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision cf19ac5f18a2.

Original comment by gregnea...@mac.com on 24 Mar 2014 at 12:45

GoogleCodeExporter commented 9 years ago 
Working fine now. Screenshot attached

Thanks

Original comment by nbalonso on 24 Mar 2014 at 2:20

Attachments:

GoogleCodeExporter commented 9 years ago 
Interestingly, even before the fix, the detail page would display OK (if you 
could get to it). The Software list page and the My Items pages would fail to 
build if an item had a non-ASCII character in the display_name.

Unicode handling in Python 2.x is full of pitfalls and dark corners; every time 
I think I have it figured out, I find out I don't. I imagine that there are 
still Unicode issues lurking about.

Original comment by gregnea...@mac.com on 24 Mar 2014 at 3:07

GoogleCodeExporter commented 9 years ago 
The detail page would display if it was previously cached/viewed. Once MSc 
closed, you couldn't view it again.

Original comment by eriknico...@gmail.com on 25 Mar 2014 at 8:44