[Rubygems-developers] Source caches again.

Hugh Sasse hgs at dmu.ac.uk
Wed Aug 29 11:36:06 EDT 2007


On Wed, 29 Aug 2007, Gregory Brown wrote:

> On 8/29/07, Hugh Sasse <hgs at dmu.ac.uk> wrote:
> > On Tue, 28 Aug 2007, Ryan Davis wrote:
> >
> > >
> > > On Aug 28, 2007, at 02:32 , Hugh Sasse wrote:
> > > > On Mon, 27 Aug 2007, Ryan Davis wrote:
> > > >> On Aug 24, 2007, at 03:45 , Hugh Sasse wrote:
> > > >>> On Thu, 23 Aug 2007, Eric Hodel wrote:
> > > >>>> It looks like gem can't talk to gems.rubyforge.org at all.
> > > >>>> What does `gem install -d flog` output?
> > > >>>
> > > >>> I've replied to this, but my reply, even compressed is too big, so
> > > >>> it's being moderated
> > > >> Put it on http://pastie.caboo.se/ or something similar (that is
> > > >> persistent for a few weeks--Eric just left for vacation).
> > >
> > > Unfortunately, the log is useless. By line 31 there is no relevant
> > > info (it is all rdoc output) and there is nothing network related,
> > > which is what I think Eric was hoping for.
> > >
> > > Does it still reproduce?
> >
> > I get flog-1.1.0 now, so it works now.  I don't know what changed.
> > I still think we need a command to flush the caches.
> 
> $ gem -v
> 0.9.4
> 
> $ sudo gem sources --clear-all
> *** Removed user source cache ***
> *** Removed system source cache ***

Thanks.  I managed to miss that.

:r! gem help source | grep cache | wc
       0       0       0

no mention of the cache in there.  I'll try to work up a doc patch

        Hugh



More information about the Rubygems-developers mailing list