-
Notifications
You must be signed in to change notification settings - Fork 141
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
Broken symlink in gem (find_error.py) #176
Comments
I guess RubyGems recently started supporting symlinks when packaging, which is why this all of a sudden became a problem. |
Note that this is a showstopper for many environments in which the gem is used. |
We @vogellacompany would really like to adapt pygments.rb for our tutorials but this issue breaks compatibility with JRuby, on which we depend. |
resolves #176 exclude find_error.py symlink from gem
@mojavelinux Somehow this doesn't fix the issue for me, please reopen.
|
Sorry, but whoever released the gem didn't do it correctly. The exclusion in the gemspec didn't execute properly and is absent from the distributed package (thus including the symlinks). If you build the gem yourself and install it, you'll find that it works. |
Actually, the gemspec in the released package is correct. So wherever the release task was run from isn't compatible with the exclusion commands (either git or find). My guess is find. I tested on a Linux box. |
Another extremely simple way to fix this problem is to have the Rake tasks that pulls down the pygments repo delete the symlink. It already deletes other files. See https://github.com/tmm1/pygments.rb/blob/dfa203797fa293822966a7479162de203127dca6/Rakefile#L46-L51. |
@mojavelinux Thank you! I've build the gem locally and can confirm that it works but I'm still having problems when running it with JRuby. I can confirm that those exact gem versions (asciidoctor and pygments.rb) run fine on MRI/CRuby.
|
For some reason, when the gem is packaged and subsequently installed, the symlink from find_error.py to debug_lexer.py in vendor/pygments-main/scripts. Perhaps we can either delete this symlink or reify it during packaging.
The text was updated successfully, but these errors were encountered: