[#30995] [Bug #3523] win32 exception c0000029 on exit using fibers — B Kelly <redmine@...>

Bug #3523: win32 exception c0000029 on exit using fibers

19 messages 2010/07/02

[#31100] [rubysoc] Queue C-extension patch to come — Ricardo Panaggio <panaggio.ricardo@...>

Hello,

26 messages 2010/07/07
[#31148] Re: [rubysoc] Queue C-extension patch to come — Roger Pack <rogerdpack2@...> 2010/07/09

> As this it my first patch to Ruby, I don't know where to begin with.

[#31320] Re: [rubysoc] Queue C-extension patch to come — Ricardo Panaggio <panaggio.ricardo@...> 2010/07/16

Sorry for leaving this thread for so long. I've tried to finish the

[#31322] Re: [rubysoc] Queue C-extension patch to come — Aaron Patterson <aaron@...> 2010/07/16

On Sat, Jul 17, 2010 at 06:55:35AM +0900, Ricardo Panaggio wrote:

[#31324] Re: [rubysoc] Queue C-extension patch to come — Caleb Clausen <vikkous@...> 2010/07/17

NB: I am Ricardo's mentor for this project.

[#31331] Re: [rubysoc] Queue C-extension patch to come — Benoit Daloze <eregontp@...> 2010/07/17

On 17 July 2010 06:00, Caleb Clausen <vikkous@gmail.com> wrote:

[#31332] Re: [rubysoc] Queue C-extension patch to come — Caleb Clausen <vikkous@...> 2010/07/17

On 7/17/10, Benoit Daloze <eregontp@gmail.com> wrote:

[#31138] Why is there no standard way of creating a String from a char *? — Nikolai Weibull <now@...>

Hi!

14 messages 2010/07/08
[#31146] Re: Why is there no standard way of creating a String from a char *? — Urabe Shyouhei <shyouhei@...> 2010/07/09

(2010/07/09 7:04), Nikolai Weibull wrote:

[#31149] Re: Why is there no standard way of creating a String from a char *? — Nikolai Weibull <now@...> 2010/07/09

On Fri, Jul 9, 2010 at 06:20, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:

[#31150] Re: Why is there no standard way of creating a String from a char *? — Urabe Shyouhei <shyouhei@...> 2010/07/09

(2010/07/09 18:28), Nikolai Weibull wrote:

[#31217] [Bug #3562] regression in respond_to? — Aaron Patterson <redmine@...>

Bug #3562: regression in respond_to?

14 messages 2010/07/12

[#31269] [Bug #3566] memory leak when spawning+joining Threads in a loop — Eric Wong <redmine@...>

Bug #3566: memory leak when spawning+joining Threads in a loop

14 messages 2010/07/13

[#31399] [Backport #3595] Theres no encoding to differentiate a stream of Binary data from an 8-Bit ASCII string — Dreamcat Four <redmine@...>

Backport #3595: Theres no encoding to differentiate a stream of Binary data from an 8-Bit ASCII string

17 messages 2010/07/21

[#31459] [Bug #3607] [trunk/r28731] Gem.path has disappeared? — Ollivier Robert <redmine@...>

Bug #3607: [trunk/r28731] Gem.path has disappeared?

22 messages 2010/07/23

[#31519] [Bug #3622] Net::HTTP does not wait to send request body with Expect: 100-continue — Eric Hodel <redmine@...>

Bug #3622: Net::HTTP does not wait to send request body with Expect: 100-continue

9 messages 2010/07/28

[ruby-core:31250] Re: [Bug #3564] 'gem uninstall' doesn't remove executables which were installed with --format-executable option

From: James Tucker <jftucker@...>
Date: 2010-07-13 13:32:49 UTC
List: ruby-core #31250
On 13 Jul 2010, at 06:11, Kenta Murata wrote:

> Bug #3564: 'gem uninstall' doesn't remove executables which were installed with --format-executable option
> http://redmine.ruby-lang.org/issues/show/3564
> 
> Author: Kenta Murata
> Status: Open, Priority: Normal
> Category: lib, Target version: 1.9.2
> ruby -v: ruby 1.9.2dev (2010-07-11 revision 28613) [x86_64-darwin10.4.0]
> 
> 'gem uninstall' command doesn't remove executables installed with --format-executable option, but ones installed without the option.
> The command, unfortunately, doesn't allow us the option so we are obliged to remove the executables manually.
> 
> Operation Log:
> 
> [12:15:24#104]mrkn$ ls /opt/rubies/bin/spec*
> /opt/rubies/bin/spec       /opt/rubies/bin/spec-1.9.2
> [14:03:11#105]mrkn$ gem-1.9.2 uninstall --format-executable rspec
> ERROR:  While executing gem ... (OptionParser::InvalidOption)
>    invalid option: --format-executable
> [14:03:47#106]mrkn$ gem-1.9.2 uninstall rspec
> Remove executables:
>        autospec, spec
> 
> in addition to the gem? [Yn]  y
> Removing autospec
> Removing spec
> 
> You have requested to uninstall the gem:
>        rspec-1.3.0
> addressable-2.1.2 depends on [rspec (>= 1.0.8)]
> autotest-growl-0.2.4 depends on [rspec (>= 1.3.0)]
> bundler-0.9.26 depends on [rspec (>= 0)]
> g-1.4.0 depends on [rspec (>= 0)]
> If you remove this gems, one or more dependencies will not be met.
> Continue with Uninstall? [Yn]  y
> Successfully uninstalled rspec-1.3.0
> [14:04:24#107]mrkn$ ls /opt/rubies/bin/spec*
> /opt/rubies/bin/spec-1.9.2


This is a known issue in RubyGems, I have proposed that --format-executable be removed as a command line option from the install command, and only exist in the configuration (gemrc). This way behaviour will be consistent unless the user explicitly changes the configuration. I have not yet come around to writing either solution, or removing the option.

There is a core problem with this whereby RubyGems does not maintain a manifest of items installed, and as such it is not aware at the time of uninstall, which binary name was installed with the package. Arbitrary use of the format executable parameter to install is for now, very much not recommended.

This bug should be reported to one of the RubyGems trackers, either at:

 http://help.rubygems.org

or

 http://rubyforge.org/tracker/?group_id=126

Please do note though, that this is a dup of a bug already in the rubyforge tracker:

 http://rubyforge.org/tracker/index.php?func=detail&aid=25826&group_id=126&atid=575

Thank you for the report. This ticket may be closed on the ruby redmine.

In This Thread