Skip to content
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

Files in axiom-types and descendants_tracker gems use 400 and 440 modes #1989

Closed
jeremyevans opened this Issue Sep 19, 2014 · 4 comments

Comments

Projects
None yet
2 participants
@jeremyevans
Copy link
Contributor

jeremyevans commented Sep 19, 2014

Issues in both upstream repos have been filed, with no response since May 23:

According to @headius, these gems are pulled in because they are transitive dependencies for jar-dependencies, which may not even need to be shipped.

@mkristian

This comment has been minimized.

Copy link
Member

mkristian commented Sep 20, 2014

may I ask where exactly the problem lies ?

yes, jruby-complete.jar does not contain those. jar-dependencies will install those gem on the fly when needed. the idea was to minimize the "download" when you first use jar-dependencies since even with ruby-maven already installed it will first download the half the internet. the second run is fast since the download is cached in the local maven repository.

the above gems are used for a pure ruby version of maven-model - let me see if jar-dependencies will work without those.

@jeremyevans

This comment has been minimized.

Copy link
Contributor Author

jeremyevans commented Sep 20, 2014

This isn't about jruby-complete.jar or using jar-dependencies. It's the simple fact that release tarballs should not contain files that are not group and world readable. Really, this should be fixed upstream, but since upstream is ignoring the issue, JRuby should work around this.

I only noticed the problem because I'm the JRuby port maintainer for OpenBSD, and the OpenBSD porting tools complain if you try to create a package that contains files that aren't group and world readable.

@mkristian

This comment has been minimized.

Copy link
Member

mkristian commented Sep 20, 2014

are the any requirements on directory permissions - if so please reopen the issue here or just leave a comment.

@mkristian mkristian closed this Sep 20, 2014

@jeremyevans

This comment has been minimized.

Copy link
Contributor Author

jeremyevans commented Sep 25, 2014

Looks like this is still a problem in 1.7.16:

ls -l jruby-1.7.16/lib/ruby/gems/shared/gems/descendants_tracker-0.0.4/TODO
-rw-r-----  1 jeremy  jeremy  0 Sep 25 12:33 jruby-1.7.16/lib/ruby/gems/shared/gems/descendants_tracker-0.0.4/TODO

mkristian added a commit that referenced this issue Sep 26, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.