Repository navigation
ruby-chef broken #186
Description
Activity
You may be able to get away with editing the specs to remove the specific version constraint, often it will just work with newer versions anyway.
As for updating the package to work against the newer ruby libraries, they're now shipping IPS packages instead of the SVR4 ones so this will be more difficult and probably mean we'll need to roll our own. This may take a while.
Do you mean that this error is being thrown because of the spec directory in my cookbooks?
No, the specs in chef. So for example, this error:
Could not find 'net-ssh' (~> 4.2) - did find: [net-ssh-5.0.2]If you search through the chef files for where it specifies
~> 4.2which from memory means 4.2 or newer but not greater than 4.x, and change it to a value where 5.x (maybe just>= 4.2I think) is permitted then you might it just works. I've done this before with various packages, developers tend to be on the conservative side when specifying dependency matches.Obviously it's a hack, but may get things working until the package can be updated.
- added a commit that references this issue
on Jul 1, 2019 - added a commit that references this issue
on Nov 24, 2019 - added a commit that references this issue
on Jan 11, 2020 - added 2 commits that reference this issue
on Mar 25, 2020 98 remaining items
- added 2 commits that reference this issue
on May 14, 2026 - added a commit that references this issue
on May 19, 2026 - added 8 commits that reference this issue
on May 22, 2026 - added a commit that references this issue
on Jun 7, 2026 - added a commit that references this issue
on Aug 7, 2026 - added a commit that references this issue
on Aug 25, 2026 - added a commit that references this issue
on Sep 6, 2026
In a global zone, with pkgsrc-tools
But...
Meanwhile, in a zone:
But...
This happens with 2017Q4 and 2018Q4.