-
Notifications
You must be signed in to change notification settings - Fork 9
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
Require issue reintroduced in 4.0.0 #11
Comments
To fix it, follow instructions provided by @rmg in #2 (comment) |
Hi, thanks for the ticket! Turns out we ran into the same problem. We just added the read permissions for others.
EDIT: To be more precise and help others to potentially find this issue more easily I added the error message we got from our pipeline. This is the error message we got when we removed the colored2 gem in version 4.0.0 and installed version 3.1.2 to use with Puppet 8:
|
Please let me know if 4.0.2 fixes this problem. |
Hi, thanks for letting me know! I will be on site towards mid of the week. Then I can verify it. So far I extracted the data.tar.gz from the colored2 4.0.3 gemfile and that looked good regarding the file rights. But real confirmation has to wait until Wednesday/Thursday. |
Version 4.0.3 fixes the issue: romuald@dvs00002 ~ 07:18:51 $ ls -lah /opt/puppetlabs/puppet/lib/ruby/gems/3.2.0/gems/colored2-4.0.3/lib/colored2.rb
-rw-r--r-- 1 root root 2,5K 21 janv. 07:18 /opt/puppetlabs/puppet/lib/ruby/gems/3.2.0/gems/colored2-4.0.3/lib/colored2.rb
romuald@dvs00002 ~ 07:19:36 $ ls -lah /opt/puppetlabs/puppet/lib/ruby/gems/3.2.0/gems/colored2-4.0.3/lib/colored2/
total 32K
drwxr-xr-x 2 root root 4,0K 21 janv. 07:18 .
drwxr-xr-x 3 root root 4,0K 21 janv. 07:18 ..
-rw-r--r-- 1 root root 2,2K 21 janv. 07:18 ascii_decorator.rb
-rw-r--r-- 1 root root 1,1K 21 janv. 07:18 codes.rb
-rw-r--r-- 1 root root 336 21 janv. 07:18 numbers.rb
-rw-r--r-- 1 root root 138 21 janv. 07:18 object.rb
-rw-r--r-- 1 root root 138 21 janv. 07:18 strings.rb
-rw-r--r-- 1 root root 71 21 janv. 07:18 version.rb @kigster Many thanks for this quick fix! |
Anytime. Thanks for the verification. The update to the |
Hi, was able to test it today. Can confirm the issue is fixed. |
Exactly the same issue than #2 have been reintroduced in 4.0.0 as described by @arkirchner .
The text was updated successfully, but these errors were encountered: