[Rubygems-developers] [ rubygems-Bugs-27872 ] 1.3.6 & quot; gem unpack& quot; fails with & quot; You don't have write permissions& quot; error

noreply at rubyforge.org noreply at rubyforge.org
Thu Mar 4 03:14:35 EST 2010


Bugs item #27872, was opened at 2010-02-22 11:07
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=27872&group_id=126

Category: None
Group: v1.3.x
Status: Closed
Resolution: Accepted
Priority: 3
Submitted By: Timothy Jones (tjones)
Assigned to: Eric Hodel (drbrain)
Summary: 1.3.6 "gem unpack" fails with "You don't have write permissions" error

Initial Comment:
Running "gem unpack" version 1.3.6 as a non-root user (without write permissions into the system gem repository) fails with a permissions error, even though the target directory IS writable.

This appears to be a 1.3.6 regression as it worked properly before.

----------------------------------------------------------------------

>Comment By: Chad Woolley (thewoolleyman)
Date: 2010-03-04 01:14

Message:
The RubyGems test suite runs under Continuous Integration here:

http://ci.pivotallabs.com:3333/builds/RubyGems

If a particular feature is not covered by the test suite, patches to the test suite are welcome.

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2010-03-04 00:20

Message:
http://rubyforge.org/tracker/index.php?func=detail&aid=27868&group_id=126&atid=575 is more important, but I have no confirmation of a fix.

You mean RubyGems should have a test suite like the one in the test directory?

----------------------------------------------------------------------

Comment By: Timothy Jones (tjones)
Date: 2010-03-03 13:31

Message:
Understood.  Perhaps you might consider automated testing in the future to 
prevent such regressions and maintain the integrity of the project.

----------------------------------------------------------------------

Comment By: Luis Lavena (luislavena)
Date: 2010-03-03 13:22

Message:
I think this issue is less critical than others like actual gem loading.

At any time you can checkout the code from the repository and install yourself (ruby setup.rb)

Each project has it's own release process, your annoyance level is not the priority, the whole project integrity is.


----------------------------------------------------------------------

Comment By: Timothy Jones (tjones)
Date: 2010-03-03 12:55

Message:
I think a patch release should be issued for this ASAP.  It is highly annoying.

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2010-02-23 23:00

Message:
Fixed in r2458

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=27872&group_id=126


More information about the Rubygems-developers mailing list