-
Notifications
You must be signed in to change notification settings - Fork 117
Fails to download with librarian-chef #105
Comments
The last release to successfully download was 1.6.1, and the first to fail was 1.7.0. |
The breaking change should be somewhere in here... v1.6.1...v1.7.0 |
@brian-beckett-hp, unfortunately we moved away from Librarian a long time back. We left the Cheffile in there as kind of a backwards-compatibility thing, but I'll admit we haven't really taken the time to make sure it still works. I can try to circle back sometime soon, but I'm not really equipped off-hand to debug unfortunately :( We will figure it out though. No ideas off the top of my head. |
I hadn't even noticed your Cheffile in there! :) I didn't think you needed one for just downloading the package with Librarian... The issue isn't urgent for me, as I was able to find an alternative Zookeeper cookbook that currently suits my needs. If you are able to resolve it at some point, that would be really great, but at least now there's a record of the issue that might save someone else from tearing their hair out over it ;) Thanks for the response! |
These errors seems to be related with the way the cookbook is being uploaded to the Supermarket. Seems to be compressed using POSIX tar format instead of GNU tar. The problem arises because there are some directories called PaxHeader when the cookbook is extracted. More details about this problem in Berkshelf issue #1132. I think librarian-chef PR #41 fixes this problem for librarian. For example, testing this cookbook with test-kitchen
File content example:
Other related errors:
|
@zuazo I can confirm your PR for librarian-chef fixes this, and I pulled it into my fork. Unfortunately, it looks like main Seems like fixes for this would be
|
I'm attempting to download the SimpleFinance/chef-zookeeper cookbook with Librarian-Chef 0.0.4. I'm using the following Cheffile:
I'm running Librarian-Chef like so:
$ librarian-chef install --verbose
Librarian-Chef fails with the following stacktrack:
The important bit from all that was:
I've not seen this before with any other Chef cookbooks, and a similar StackOverflow question indicates that the cookbook may be at fault in some way.
So... any thoughts? Are you able to replicate this issue at all?
The text was updated successfully, but these errors were encountered: