-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
makecatalogs.munki fails with UnicodeEncodeError #604
Comments
Hi @workflowsguy - |
Does it help if you set the environment variable PYTHONIOENCODING to utf-8 when running AutoPkg (run Long story short, I was debugging a similar issue with MunkiAdmin where makecatalogs would run perfectly when in Terminal but would fail when being called by external process. Python 3 seems to treat terminal output differently than piping the output to another command. Not really knowing enough about this I’d appreciate if someone with more Python 3 experience could explain why this is happening and what would be the best solution. |
Similar problem here: OS version: Mojave 10.14.6 |
Did a update to Munki 4.0.1.3899, seems to get rid of the error |
I am able to reproduce this on Munki tools 4.0.1 with either AutoPkg 1.4.1 or AutoPkg 2.0 RC1, if there's a non-ASCII file/folder path in the Munki repo. (Verbose log: https://gist.github.com/homebysix/aac010cce244d4e12a7bad38a1417665) @workflowsguy, could you run this on your Munki repo and see whether any files appear?
|
@homebysix , apologies for the late reply. Running
|
I get this output, the first one seems reporting right, but the second "Skolkorridoren Kyocera P6035.plist" When I added underscore instead "Skolkorridoren_Kyocera_P6035.plist" the file doesn't show up when searching. Thanks!
• Stripped out, but same name as another files in same path |
autopkg 2.1: |
What are the chances of this issue getting addressed anytime soon? I have more and more packages that I cannot install with Munki because they contain Umlauts or accented characters in the package or developer name. |
Does this repro with any recipes right now in North American English locale? Or if you can provide an exact repro case, that would be helpful. |
If it's only MakeCatalogs.munki that is failing, a workaround would be to not run that recipe as part of a recipe list, and to run It's kind of over-stating things to claim "I have more and more packages that I cannot install with Munki because they contain Umlauts or accented characters in the package or developer name." because of this issue, since the workarounds are easy and straight-forward. |
if you need any additional information besides what i have already given in previous posts, please tell me what you need. |
It is not my main job to be a system admin, i have to do this in addition to my regular work. So a workaround to an issue that might be "easy and straight-forward" to you as the creator/maintainer of Munki is not to me. |
Fair enough. We’re all volunteers here, working on things in our spare time. I’m just suggesting alternative solutions you could explore to at least address it for yourself. |
Describe the problem
Since the upgrade to Munki 4, the makecatalogs.munki recipe keeps failing with the following error:
Version (please complete the following information):
The text was updated successfully, but these errors were encountered: