-
Type:
Task
-
Status: Closed
-
Priority:
Normal
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: PUP 5.0.0
-
Component/s: None
-
Template:customfield_10700 114060
-
Epic Link:
-
Team:Agent
-
Story Points:5
-
Sprint:Agent 2017-04-05, Agent 2017-04-19, Agent 2017-05-03, Agent 2017-05-31
-
Release Notes:Deprecation
-
Release Notes Summary:Puppet previously shipped and/or depended on the win32-eventlog gem for its interface to the windows in eventlog. In puppet 5, this dependency has been removed and puppet interfaces with eventlog directly.
-
QA Risk Assessment:No Action
-
QA Risk Assessment Reason:Tested in spec
Remove the references for the Win32-Eventlog gem from Puppet
Also check for 3rd party dependencies
- blocks
-
PA-1129 Remove win32-eventlog gem from packages
-
- Closed
-
- duplicates
-
PUP-5755 Replace win32-eventlog calls with internal API implementations that are wide-string compatible
-
- Closed
-
- is blocked by
-
PUP-7498 Puppet merges two users in different encodings into one
-
- Closed
-
- is duplicated by
-
PUP-1441 --show_diff causes crashes on files with UTF-8 content
-
- Closed
-
-
PUP-7063 Handle incompatible encodings in Puppet::Util::Log when rendering to console
-
- Closed
-
- relates to
-
PCP-733 tests/pxp-module-puppet.run_puppet_nonASCII.rb fails on Japanese machines
-
- Closed
-
-
PUP-7880 When logging mixed encoding strings, Puppet may fail
-
- Closed
-
-
PUP-7063 Handle incompatible encodings in Puppet::Util::Log when rendering to console
-
- Closed
-
-
PUP-5560 Look at Improving Unicode for all Windows gems
-
- Resolved
-
-
PUP-5755 Replace win32-eventlog calls with internal API implementations that are wide-string compatible
-
- Closed
-
-
PUP-3551 Sanitize non-UTF-8 data in run reports
-
- Ready for Engineering
-