win32-service has some ANSI API calls that may cause problems in a non-US language environment. This ticket should involve replacing API calls internally where applicable, and PUP-xxx involves the mechanics of removing the gems from puppet-win32-ruby, etc.
win32-service has some ANSI API calls that may cause problems in a non-US language environment.
This ticket should involve replacing API calls internally where applicable, and PUP-xxx involves the mechanics of removing the gems from puppet-win32-ruby (should that be necessary), etc. The current gem implements our service hosting, so it may be OK to leave this in place for now - but make patches to our local copy of the gem in {{puppet-win32-ruby}} and propose the same changes to the upstream gem.
win32-service has some ANSI API calls that may cause problems in a non-US language environment.
This ticket should involve replacing API calls internally where applicable, and PUP-xxx5758 involves the mechanics of removing the gems from puppet-win32-ruby (should that be necessary), etc.
The current gem implements our service hosting, so it may be OK to leave this in place for now - but make patches to our local copy of the gem in {{puppet-win32-ruby}} and propose the same changes to the upstream gem.
- Puppet can manage a service that has Unicode display names and descriptions. - Puppet service provider and daemon no longer depend on the win32-service gem.
win32-service has some ANSI API calls that may cause problems in a non-US language environment.*In Scope* This ticket should involve replacing API calls internally where applicable, and PUP-5758 involves the mechanics* Replace existing uses of removing the gems from puppet-win32-ruby (should that be necessary) Win32::Service, etc.
The current gem implements our primarily in provider/ service hosting/windows & tests, so it may be OK to leave this in place for now - but make patches to our local copy of with the gem API defined in {{puppet PUP-win32-ruby}} and propose the same changes to the upstream gem.7990