-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
librarian stopped working with latest minitar v1 release #122
Comments
This was merged and released
There was 4bf2503 (which has a wrong summary). Let's create a new release that includes it. |
Any chance for this new release of |
+1, I am having this issue as well. To work around it, I downgraded to minitar 0.12.1. |
@bastelfreak can you tag a new release that includes 4bf2503? It's been over 3 months now where librarian is straight up broken without a workaround. |
Hi, |
@der-eismann FWIW I downgraded minitar to pre-1.0 and this worked for me to get librarian working great again. |
It turns out that the
puppet_forge
gem has a dependency on minitar without a version requirement on it (https://github.com/puppetlabs/forge-ruby/blob/main/puppet_forge.gemspec#L26) and is still using the oldarchive/tar/minitar
namespace. However a few days ago minitar had it's v1 major release, abandoning the old namespace, causing issues with librarian:I opened puppetlabs/forge-ruby#119 to fix this temporarily, however librarian isn't even using
forge-ruby v5
and I'm not sure if/when this change will land. Maybe this helps someone else or somebody at puppet can speed things up a bit, it feels like the whole ecosystem is pretty outdated unfortunately.My workaround so far:
The text was updated successfully, but these errors were encountered: