No such cookbook: mingw
mvaal opened this issue · 7 comments
Cookbook version
2.1.0
Chef-client version
14.2.0
Platform Details
Windows 10 using Docker for Windows
Scenario:
run a successful kitchen verify command
Steps to Reproduce:
chef generate cookbook mingw_test
Add depends 'mingw', '>= 2.1.0' to metadata.rb.
Modify .kitchen.yml with
driver:
name: docker
socket: npipe:////./pipe/docker_engine
Run kitchen verify
Expected Result:
Successful completion of kitchen verify
Actual Result:
resolving cookbooks for run list: ["mingw_test::default"]
================================================================================
Error Resolving Cookbooks for Run List:
================================================================================
Missing Cookbooks:
------------------
No such cookbook: mingw
Expanded Run List:
------------------
* mingw_test::default
System Info:
------------
chef_version=14.3.37
platform=centos
platform_version=7.5.1804
ruby=ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux]
program_name=/opt/chef/bin/chef-client
executable=/opt/chef/bin/chef-client
This happens for any chef recipe that has a dependency on mingw. Thanks.
Hey There
It looks like this is the first issue you've filed against the chef-cookbooks project. I'm here to offer you a bit of extra help to make sure we can quickly get back to you.
Make sure you've filled out all the fields in our issue template. Make sure you've provided us with the version of chef-client you're running, your operating system and the version of the cookbook. If you're not using the most up to date version of the cookbook then please make sure to update first. Lots of things change between versions even if you're issue isn't listed in the changelog. Finally please give us a detailed description of the issue you're having. The more we know about what you're trying to do, what actually happens, and how you can reproduce the problem, the better.
If you're looking for more immediate troubleshooting help make sure to check out #general on the Chef Community Slack. There's plenty of folks there willing to lend a helping hand. Thanks for the first issue. We hope we can get back to you soon with a solution.
You may just need to do a berks update in the test cookbook directory before running.
Thanks, I have tried that. The Berks file ends up looking like this:
DEPENDENCIES
mingw_test
path: .
metadata: true
GRAPH
logrotate (2.2.0)
mingw_test (0.1.0)
mingw (>= 2.1.0)
seven_zip (3.0.0)
windows (>= 0.0.0)
windows (5.0.0)
The error is still there.
I even tried to do a berks vendor to a directory and mingw doesn't show up in the output directory.
So out of curiosity how do you plan to run this cookbook on CentOS when it's for setting up build tools on Windows?
This is just a sample application to reproduce, we are running recipe that uses rabbitmq (5.6.1) which ends up using
build-essential (8.1.1)
mingw (>= 1.1)
as a dependency. I am unsure why mingw is being pulled in, but since it is a dependency it is trying to pull it (but not finding it). This issue does not show up on Mac, but I am seeing it on my Windows machine running Chef DK.
In other words you can replace
depends 'mingw', '>= 2.1.0'
with
depends 'rabbitmq', '>= 5.3.0'
in metadata.rb and get the same result.
Marking stale due to inactivity. Remove stale label or comment or this will be closed in 7 days. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help! Thanks, Sous-Chefs.
Closing due to inactivity. If this is still an issue please reopen or open another issue. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help! Thanks, Sous-Chefs.