Home → Problems →

Marshal.4.8.Z still not updating completely, as of 21 September

• Edit

cwalquist

21 Sep, 2010 03:14 PM

mongo 1.0.9 in particular is not being included. Latest version in Marshal.4.8.Z is 1.0.7.

-chris

Related to this discussion: http://help.rubygems.org/discussions/problems/306-marshal48z-not-up...

$ gem sources CURRENT SOURCES

http://gems.us.drwholdings.com:8808/
http://gems-mirror.us.drwholdings.com:8808/
$ gem list --remote mongo$

REMOTE GEMS

mongo (1.0.7)
$ gem list --remote --source http://gemcutter.org/ mongo$

REMOTE GEMS

mongo (1.0.9)

$

---

Selected output from log:

fetching: http://gemcutter.org/Marshal.4.8.Z
Fetching 71907 gems
... 11763/71907: mongo-1.0.7.gem
... 11770/71907: mongo-1.0.6.gem
... 11775/71907: mongo-1.0.5.gem
... 11783/71907: mongo-1.0.4.gem
... 11790/71907: mongo-1.0.3.gem
... 11796/71907: mongo-1.0.2.gem
... 11800/71907: mongo-1.0.1.gem
... 11803/71907: mongo-1.0.gem
... Tue Sep 21 02:01:28 CDT 2010
Loading 72659 gems from /data/rubygems.mirror
... 10474/72659: mongo-1.0.3
... 17478/72659: mongo-1.0.1
... 30677/72659: mongo-1.0.2
... 30792/72659: mongo-1.0.5
... 44831/72659: mongo-1.0.7
... 49249/72659: mongo-1.0.6
... 52597/72659: mongo-1.0.4
... 65359/72659: mongo-1.0
... Loaded all gems
loaded: 2900.960s
Generating Marshal quick index gemspecs for 72656 gems
... 6468/72656: mongo-1.0
... 60715/72656: mongo-1.0.1
... 60721/72656: mongo-1.0.2
... 60725/72656: mongo-1.0.3
... 60731/72656: mongo-1.0.4
... 60734/72656: mongo-1.0.5
... 60740/72656: mongo-1.0.6
... 60747/72656: mongo-1.0.7
... Complete
Generated Marshal quick index gemspecs: 30.017s
Generating YAML quick index gemspecs for 72656 gems
... 6370/72656: mongo-1.0
... 59524/72656: mongo-1.0.1
... 59526/72656: mongo-1.0.2
... 59530/72656: mongo-1.0.3
... 59538/72656: mongo-1.0.4
... 59544/72656: mongo-1.0.5
... 59548/72656: mongo-1.0.6
... 59551/72656: mongo-1.0.7
... 71241/72656: rails3-tutorial-0.4.1
Complete
Generated YAML quick index gemspecs: 358.995s
Generating quick index
Generated quick index: 3.016s
Generating latest index
Generated latest index: 2.878s
Generating Marshal master index
Generated Marshal master index: 6.436s
Generating YAML master index for 72656 gems (this may take a while)
... 37145/72656: mongo-1.0
37146/72656: mongo-1.0.1
37147/72656: mongo-1.0.2
37148/72656: mongo-1.0.3
37149/72656: mongo-1.0.4
37150/72656: mongo-1.0.5
37151/72656: mongo-1.0.6
37152/72656: mongo-1.0.7
37153/72656: mongo-find_replace-0.18.3
... 72656/72656: zyps-0.7.6
Complete
Generated YAML master index: 389.056s
Generating specs index
Generated specs index: 2.802s
Generating latest specs index
Generated latest specs index: 2.323s
Generating prerelease specs index
Generated prerelease specs index: 0.018s
Compressing indicies
Compressed indicies: 4.667s
Moving index into production dir /data/rubygems.mirror

1. 1 Posted by Kent Cowgill on 22 Sep, 2010 08:19 PM

   

   mailbox-0.2.5 didn't update last night either :(

   • Edit

2. 2 Posted by cwalquist on 24 Sep, 2010 01:48 PM

   

   Bundler too is behind.

   $ gem list bundler --remote --source http://gems-mirror.us.drwholdings.com:8808/

   REMOTE GEMS

   bundler (0.9.26)
   bundler08 (0.8.5)
   $ gem list bundler --remote --source http://gemcutter.org
   REMOTE GEMS

   bundler (1.0.0)
   bundler08 (0.8.5)
   $

   • Edit

3. 3 Posted by João Duarte on 27 Sep, 2010 06:42 PM

   

   Anyone else also getting this while doing "gem1.8 generate_index --no-legacy --modern --update"?

   Generating Marshal quick index gemspecs for 272 gems
   ................................................................................................................................................................................................................................................................................ERROR: While executing gem ... (RangeError)

   bignum too big to convert into `long'

   • Edit

4. 4 Posted by cwalquist on 30 Sep, 2010 04:10 PM

   

   Any progress? We are having to manually fetch individual gems in the middle of the day and rebuild the internal mirror index.

   Thanks,
   -chris

   • Edit

5. 5 Posted by Kent Cowgill on 05 Oct, 2010 02:31 PM

   

   FYI,

   I noticed this morning that "gem generate_index --no-legacy --modern --update -d [/path/to/gem.mirror] looks like it works, but doesn't actually update our own latest_specs.4.8.gz.

   I had to manually fetch ice_cube 0.59 and tried running the above command and got this output:

   Loading 1 gems from /data/rubygems.mirror
   1/1: ice_cube-0.5.9
   Loaded all gems
   loaded: 0.002s
   Generating Marshal quick index gemspecs for 1 gems
   1/1: ice_cube-0.5.9
   Complete
   Generated Marshal quick index gemspecs: 0.000s
   ERROR:  While executing gem ... (NoMethodError)
     undefined method `<=>' for nil:NilClass
         /site/apps/ruby-1.8.6/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:704:in `<=>'
         /site/apps/ruby-1.8.6/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:704:in `sort'
         /site/apps/ruby-1.8.6/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:704:in `update_specs_index'
         /site/apps/ruby-1.8.6/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:657:in `update_index'
         /site/apps/ruby-1.8.6/lib/ruby/site_ruby/1.8/rubygems.rb:933:in `time'
         /site/apps/ruby-1.8.6/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:656:in `update_index'
         /site/apps/ruby-1.8.6/lib/ruby/site_ruby/1.8/rubygems/commands/generate_index_command.rb:125:in `execute'
         /site/apps/ruby-1.8.6/lib/ruby/site_ruby/1.8/rubygems/command.rb:270:in `invoke'
         /site/apps/ruby-1.8.6/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:134:in `process_args'
         /site/apps/ruby-1.8.6/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:104:in `run'
         /site/apps/ruby-1.8.6/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run'
         /site/apps/ruby/bin/gem:21

   If I were a betting man, I'd say we're seeing the same issues with --update that rubygems.org is seeing.

   • Edit

6. Support Staff 6 Posted by Nick Quaranto on 12 Oct, 2010 12:09 AM

   

   Finally got it updated. Sorry about the delay here, folks. If you're seeing any other issues let us know.

   • Edit

7. Nick Quaranto closed this discussion on 12 Oct, 2010 12:09 AM.

8. Nick Quaranto re-opened this discussion on 12 Oct, 2010 04:36 PM

9. Support Staff 7 Posted by Nick Quaranto on 12 Oct, 2010 04:36 PM

   

   Argh...it updated, something must have gotten corrupted on the way there. I'll try running it again. The process takes 20-30 minutes and is realyl CPU intensive (needs to load all 80,000+ gemspecs into memory and then spit it back out). I'll keep this thread and the prior one updated on my progress. Rerunning this now.

   • Edit

10. 8 Posted by Christian van d... on 13 Oct, 2010 04:22 PM

    

    Any news on this? I'm still getting the corrupted header check

    • Edit

11. Support Staff 9 Posted by Nick Quaranto on 14 Oct, 2010 05:07 AM

    

    Fixed, for real this time. Sorry about the delay here, folks.

    • Edit

12. Nick Quaranto closed this discussion on 14 Oct, 2010 05:07 AM.