Unable to import gems because of write_gem failure

[ognevsky]

Another issue about importing gems locally:
This rake task rake gemcutter:import:process ~/code/gemcutter/vendor/cache aborted when write_gem method is invoked.

This is because this method https://github.com/rubygems/gemcutter/blob/master/app/models/vault.rb#L17-19 returns nil. So, the next step is directory.files, which raises undefined method 'files' for nil:NilClass.

So, based on my prev. issue I see this picture:
— if some gem has dep's, it's failure here: https://github.com/rubygems/gemcutter/blob/master/app/models/pusher.rb#L50 and then next gem's turn.
— if some gem hasn't any dep's, it failures with nil.files as I showed above. And it saved to rubygems table, too. So, the next time I started this rake task, this gem will be skipped (because no version update).

No gems are imported to /server/cache dir, but gems w/o dependencies save themselfs to DB (linksets, ownerships, versions and rubygems tables).

Sorry for my English, I hope you will understand me.

[phoet]

i came accross the same issue and created a gist with the output here: https://gist.github.com/1473589

the funny thing is that the import process continues gem by gem after each call to the rake task.

since i have no idea what is happening with the indexer and fog, i have no clue where to look for a fix :(

[ognevsky]

@phoet there was some pull request about this, but is still unmerged and i don't actually know if it solves this problem. Here it is: #294

[cmeiklejohn]

Closing.