Closed (fixed)
Project:
Community Forge - Hamlets
Version:
7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
17 Apr 2014 at 18:42 UTC
Updated:
5 May 2014 at 20:10 UTC
Jump to comment: Most recent
Comments
Comment #1
drummI deleted the unpackaged releases that had this bug. Please do not recreate them. Only make a fresh release with this fixed.
Comment #2
drummBefore making any new releases, you must fix this!
DO NOT MAKE ANOTHER rc15 release!
Comment #3
matslats commentedUnderstood thanks I was wondering why the release didn't appear!
Comment #4
matslats commentedMcnasty
Now when I made the release node for rc16 validation failed.
Perhaps I should put that line in the drupal-org-core.make?
Any ideas I'm out of my depth?
>The drupal-org.make file for project Community Forge "Hamlets" failed verification for Git tag 7.x-1.0-rc16.
http://drupal.org/node/642116 -- to learn more about correcting these errors.
Directory /tmp/drush exists, but is not writable. Please check [error]
directory permissions.
Drush must have a writable cache directory; please insure that one of [error]
the following locations is writable: /tmp
PHP Fatal error: Allowed memory size of 838860800 bytes exhausted (tried to allocate 523800 bytes) in /var/www/drupal.org/tools/drush5/includes/filesystem.inc on line 319
Once these errors are fixed, commit the changes to your drupal-org.make, move the release tag for your project (check the Git manual to learn how to move tags if necessary), and submit the release node again.
Comment #5
drummThat's a transient error, the permissions seem to be messed up on one web server. Saving again will have a decent chance of getting another, if it happens again. I'll look into fixing later.
I created the release https://drupal.org/node/2244921. I set you to the author, so feel free to edit.
And the underlying problem is mitigated, so we'll verify that a makefile doesn't include itself.
Comment #6
drummBoth underlying problems with Drupal.org are now fixed.
The site will check that a distribution won't include itself, and I fixed the permissions issue that caused #4.
Sorry for the inconvenience.