Comments

ezra-g’s picture

Project: Drupal.org infrastructure » Creative Commons
Version: » 7.x-1.x-dev
Component: Packaging » Code
Priority: Normal » Critical

I'm able to reproduce this locally. I'm continuing to troubleshoot. I noticed that Commons Posts had no releases so I created a dev snapshot release.

ezra-g’s picture

Project: Creative Commons » Drupal Commons
Version: 7.x-1.x-dev »

Oops - Sorry, CC folks.

ezra-g’s picture

Status: Active » Fixed

I resolved this by creating a dev snapshot release of Commons posts, marking it recommended and shown on the project page, and re-packaging with the --no-cache option. This should be resolved next time Drupal.org packages Commons.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

hefox’s picture

Experienced something similar to this also with open atrium and a recently prompted to full project with no published releases. Waited a day for the release and still got it, so added (projects[project_name][type] = module) and t worked (since it was easier than messing with the jenkins task).

(this is currently second result for googling that error message)