Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Sorry, I had to unpublish 7.x-26.x-dev and a new tagged releases. They caused Drupal.org's drush make go into a loop, taking all the RAM. Those releases hadn't successfully packaged in the last month anyway.
http://drupalcode.org/project/drustack.git/blame/refs/heads/7.x-26.x:/dr... should not include drustack. Since it was in build-drustack.make before, Drupal.org packaging didn't know about it. Now that it is included, it falls into a loop.
I can re-publish the release once this is fixed.
Comments
Comment #1
hswong3i CreditAttribution: hswong3i commentedSorry I didn't read this post before republish the release, please again delete it!
I will fix it as above mentioned and publish the new version later, really sorry :-(
Comment #2
hswong3i CreditAttribution: hswong3i commentedHi drumm thank you for your information and the lines had been move back to custom .make files. The new releases should be fine right now. Please feel free to check it out ;-)
Comment #3
hswong3i CreditAttribution: hswong3i commentedComment #4
drummYes, looks like the loop is gone, but there is a new, much less serious, problem:
Comment #5
hswong3i CreditAttribution: hswong3i commentedOoops...
I shouldn't miss that due to navbar...
Please kindly remove both 7.x-26.67 and 7.x-26.28...
Another new release is now working out...
Thank you very much~~~
Comment #6
hswong3i CreditAttribution: hswong3i commentedWell... Bootstrap related issue should goes to https://drupal.org/comment/8560141#comment-8560141... It is already whitelisted, but the regex is incorrect...
Comment #7
hswong3i CreditAttribution: hswong3i commented@drumm: since #1445226: Add Twitter Bootstrap to whitelist now get fixed, may I have your hand for retouch the build package action for [#2214407]?
Comment #8
hswong3i CreditAttribution: hswong3i commentedComment #9
drummYep, looks all clear.
Comment #10
hswong3i CreditAttribution: hswong3i commentedThank you very much for your kindly help ;-)