tag:help.rubygems.org,2010-01-19:/discussions/problems/306-marshal48z-not-updatedRubyGems.org: Discussion 2011-05-12T16:04:17Ztag:help.rubygems.org,2010-01-19:Comment/27709782010-09-04T03:44:47Z2010-09-04T03:44:47ZMarshal.4.8.Z not updated<div><p>Yeah, not sure why this has stopped, going to investigate this weekend and will report back. Thanks for the heads up.</p></div>Nick Quarantotag:help.rubygems.org,2010-01-19:Comment/27709782010-09-08T18:25:48Z2010-09-08T18:25:48ZMarshal.4.8.Z not updated<div><p>FYI, this seems to have hit me too on an internal rubygems.org mirror I'm running at work. It also seems to have happened a handful of times in the past (including having it out of date on our weekly sync on 9/4/10)</p></div>Kent Cowgilltag:help.rubygems.org,2010-01-19:Comment/27709782010-09-13T12:49:57Z2010-09-13T12:49:58ZMarshal.4.8.Z not updated<div><p>I notice it's still out of date.</p>
<p>Any updates on this?</p></div>Kent Cowgilltag:help.rubygems.org,2010-01-19:Comment/27709782010-09-14T15:32:42Z2011-05-12T16:04:17ZMarshal.4.8.Z not updated<div><ol>
<li>Our developers are impacted, since our dev build system
environments point to our internal gems mirror (as do our
production systems), so it's not feasible for us to point dev
builds at <a href="http://gemcutter">http://gemcutter</a>, without
also updating production...and updating production is a real
process pain (change requests, meetings, scheduling, etc.),
especially considering that our production systems are not supposed
to point to URLs outside the organization.</li>
</ol></div>cwalquisttag:help.rubygems.org,2010-01-19:Comment/27709782010-09-14T21:45:11Z2010-09-14T21:45:11ZMarshal.4.8.Z not updated<div><p>Fixed now and updating daily once again. Sorry about this, folks.</p></div>Nick Quaranto