Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#36036 - [namcap] doesn't check ruby packages correctly

Attached to Project: Arch Linux
Opened by Daniel Mendler (minad) - Friday, 05 July 2013, 16:48 GMT
Last edited by freswa (frederik) - Saturday, 22 February 2020, 15:57 GMT
Task Type Bug Report
Category Arch Projects
Status Assigned
Assigned To Rémy Oudompheng (remyoudompheng)
Kyle Keen (keenerd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


rubygem packages can be created using

These packages have the name ruby-* and depends on ruby. Furthermore they depend on other rubygems. However namcap doesn't check these packages correctly. It warns that the dependency 'ruby' and the dependencies for the other gems are unnecessary.

It might be good to add a module to namcap to check for the validity of ruby packages.
This task depends upon

Comment by Ashley Whetter (AWhetter) - Wednesday, 10 July 2013, 15:13 GMT
I'm not really sure whether or not to agree on this because using rubygems directly (ie with `gem install ..`) is used a lot.
It makes sense for stuff like python packages because they are used more than pip is, but for ruby I don't think it does really does make sense.
Comment by Mike Bonar (oldpond) - Wednesday, 04 September 2013, 09:59 GMT
Yes, there's something messed up here with the new bundle. gem install by anyone other than root requires permission changes in /usr/lib and /usr/bin even with $(ruby -rubygems -e "puts Gem.user_dir")/bin in the PATH variable.
Comment by Mike Bonar (oldpond) - Wednesday, 04 September 2013, 10:00 GMT
I should add the problem shows up when you try 'rails new demo'.
Comment by Ashley Whetter (AWhetter) - Wednesday, 04 September 2013, 10:05 GMT
@Mike: Do you mean when you use pacgem? Do you also have GEM_HOME=$(ruby -rubygems -e "puts Gem.user_dir")/ ? I ask because I don't have this issue (but I'm not using pacgem either).
Comment by Mike Bonar (oldpond) - Thursday, 05 September 2013, 11:32 GMT
@Ashley, No, I don't use pacgem. I have GEM_HOME set in my PATH.export PATH=$PATH:$(ruby -rubygems -e "puts Gem.user_dir")/bin but not GEM_HOME. It's not very consistent. I built one machine at home and all I had were path problems. This machine required me to change permissions on /usr/lib and /usr/bin. I am building my laptop now, so we will see how that one goes.
Comment by Stefan Schick (pommes_) - Sunday, 21 July 2019, 17:36 GMT
The ticket didn't get touched since february 2014. Is this still an issue?
I also tried the pacgem tool to check how namcap behaves. But pacgem itself threw an error, see