Problem with Development Release files on Drupal site?

Now it works.

I'm having the same issue

I've posted against this issue: https://drupal.org/node/2107919#comment-7951851

see below:
----
Trying to dl the latest dev version as requested in comment #3: https://drupal.org/node/2107919#comment-7949521

I'm getting a not found error, so I am blocked from testing this further.

Not Found

The requested URL /files/projects/openatrium-7.x-2.x-dev-core.tar.gz was not found on this server.

Apache Server at ftp.drupal.org Port 80

----

@mpotter, et al:

I've had this happen with my distributions when I put something in the make file that Drupal.org didn't like, for example: a library that isn't in the Drupal.org whitelist, patch that didn't apply, bad URL, etc. Sometimes it's even things that will work via "drush make" but Drupal.org breaks on.

I can't remember exactly where it is, but there is some place under your project page where it'll show you the actual error.

I don't know if this is related to OpenAtrium's problem, but I hope that helps!

As documented in comment #3 I'm blocked
Thankfully mpotter advised:

git clone to grab the distro, then drush make has an option for the drupal.org build process that allows you to build it in a separate directory and then copy over the files as if you had downloaded the tar.gz files

Steps I took to manually update dev:

.1 Grabbing Open Atrium Dev from git:

cd Dropbox/Sites/ 
#cd into where you want it to go
mkdir OA-dev
cd OA-dev
git clone --branch 7.x-2.x http://git.drupal.org/project/openatrium.git  
cd openatrium

.2 To add Drupal.org drush to my commands:

cd /Applications/drush/command
git clone http://git.drupal.org/project/drupalorg_drush.git  
cd drupalorg_drush
drush cc drush
drush verify-makefile

.3 To build the dev site form Drush make:

kae76@MBP13:/Dropbox/Sites/OA-dev$ drush make build-openatrium.make temp-dir
cd temp-dir

You can do all of these next steps in the command line however I had brain freeze and defaulted to an easier process :)
• Opened Finder and backed up my www folder with my current beta4 site in
• in the temp-dir I deleted the sites folder
• copied contents of temp-dir and over wrote in to current www folder
• I ssh into my Vagrant box

drush updb

This worked to update my version of Open Atrium.

Marking this as fixed because of the great #5 comment with the procedure on what to do when drupal.org messes up.

The distribution packager on Drupal.org tries to build the -dev version each night. But it's very finicky and can fail for a number of reasons. Unfortunately it never sends any notification to anybody about why it fails (or even that is *has* failed).

I've added a Jenkins job to our process to test the drupal.org -dev release every morning. This tells me what it is failing, but still not why.

As dsnopek mentioned, it's often some sort of missing dependency that other testing will uncover. But it's also just part of the normal life of working with Drupal. -dev versions are not meant to be 100% reliable.

Would be nice to see the packager improved to email error reports when it fails and to give the maintainer a way to trigger a new build. Not likely to see these changes until drupal.org moves to D7.

@mpotter thanks for complimenting my documentation in #5 It's nice to be acknowledged. :-)

I wonder if it needs to go anywhere useful? - as Im aware this happens a lot, not sure where to put it though