UTF8 package names on windows (invalid byte sequence)

[mail...@googlemail.com]

Hi,

I'm currently trying to install Skype's MSI using puppet.
The name of the  package returned by 'puppet resource package' is "SkypeT 6.14".
The correct one would be "Skype™ 6.14".

However, puppet fails to handle both:
If specified with the trademark sign, I get an "invalid byte sequence in US-ASCII" error.
If specified following the return value if the puppet resource, it also tries to install it again (as it does not match the windows package name).

It seems that puppet has a general problem with utf-8 characters or other special signs like umlauts [1],[2] which had not been fixed yet.
But I wasn't able to find a workaround/solution for this kind of problem.

Software in use:
Puppet Client: v3.4.3 on Windows 7 Professional (German language)
Puppet Master: v3.4.3 on Debian 7

Anyone has an idea?
Thanks in advance.

[1] https://groups.google.com/forum/#!topic/puppet-users/49ovbwcC7vs
[2] https://tickets.puppetlabs.com/browse/PUP-1225

[Rob Reynolds]

I'm not sure we have a workaround for this at the current time. I know in 3.5.0 we have made some improvements in puppet resource package. You might give the RC a try.

If that doesn't work, please file an issue on this.

As a current workaround for using the windows package resource, have you looked at chocolatey package resource?

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/91b2a79c-d7e2-4286-a267-00cfa2af11d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Rob Reynolds

Developer, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco - http://bit.ly/pupconf14
Register now and save $350!

[mail...@googlemail.com]

Hi Rob,

thanks for your answer.
I tried chocolatey as it seems to be the easiest solution and very useful for other packages on windows, too.
Chocolatey worked, but I hadn't time so far to take a look into how it handle this specific case.
Thanks for the tip.

Kind regards.