Details
-
Task
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
1
-
Week 2014-6-25 to 2014-7-9
Description
The win32-service gem was patched upstream to resolve #16080. The fix was merged upstream <https://github.com/djberg96/win32-service/pull/8>. At a minimum we need to update the gem and remove the patch <https://github.com/puppetlabs/puppet-win32-ruby/blob/1.9.3/16080-handle-missing-description.patch>. We also need to make sure we can update to the `ffi` branch of `win32-service` without running into the same problem again <https://github.com/djberg96/win32-service/pull/8#issuecomment-20688123>. Update: It appears this has been fixed in FFI-land since 0.8.3 <https://github.com/djberg96/win32-service/commit/2220e5e35f2b56a3e1c7e90154d8da6c7d6361e4>. Actually that was incorrect, so patches have been submitted upstream.
Attachments
Issue Links
- blocks
-
PUP-2396 Support ruby 2.0 x64 on windows
-
- Closed
-
-
PUP-392 Validate win32 gems on x86 and x64
-
- Closed
-
-
PUP-2521 Remove windows-pr gem as a Windows dependency
-
- Closed
-
-
PUP-2881 Upgrade win32-taskscheduler gem (or replace)
-
- Closed
-
-
PUP-2889 Upgrade win32-eventlog
-
- Closed
-
- relates to
-
PUP-6459 puppet resource service fails on Windows 10 Pro (x64)
-
- Closed
-
-
PUP-4390 Regression: Windows service provider fails to retrieve current state on 2003
-
- Closed
-
-
PUP-1471 Puppet Agent windows services accidentally comes of out Paused state
-
- Closed
-
-
PUP-3222 Windows service provider references a non-existent class
-
- Closed
-
-
PUP-391 Validate FFI'ed native windows code against Ruby 2 x64
-
- Closed
-
-
PUP-3126 Update win32-service gem to 0.8.6+
-
- Closed
-
- clones
- links to