Closed (fixed)
Project:
Drupal.org infrastructure
Component:
Other
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
19 Jan 2007 at 14:52 UTC
Updated:
21 Aug 2014 at 21:00 UTC
Jump to comment: Most recent
For the mapbuilder project 2 releases have been defined with the same name (see http://drupal.org/node/108835/release). When HEAD was still compatible with Drupal version 4.7, I created release http://drupal.org/node/109151 but now HEAD has moved on to Drupal 5.0. So I would like to make another project release for the HEAD version, but it (http://drupal.org/node/109151) needs to be removed first.
Thank you.
Comments
Comment #1
dwwi just changed the version info for your HEAD node, and re-ran the packaging script to clean up everything.
please edit the release notes for http://drupal.org/node/109151, i just reset them to something simple.
it's really odd that the release system let you add 2 release nodes with the same version string, i didn't think that was possible. ;) weird.
also, b/c of this confusion w/ 2 releases with the same version, the 2 issues in your issue queue that used to think they were "4.7.x-1.x-dev" were in fact pointing to your HEAD release, so they now think they're version "5.x-1.x-dev". you should probably followup to those 2 and re-assign them to 4.7.x.
that should be everything, please set this back to active if there's anything else.
cheers,
-derek
Comment #2
jpulles commentedThanks for your prompt fix!
I'm not certain if something is still wrong, or that i have to wait for the next batch run. The 4.7.x archive included the .info file, while according to http://cvs.drupal.org/viewcvs/drupal/contributions/modules/mapbuilder/?o... it should not be included there. So maybe the archive is not (yet) build from the correct sources?
John.
Comment #3
dwwyup, the 4.7.x tarball that was still there was the old one from HEAD, and you hadn't checked in anything to the DRUPAL-4-7 branch, so the packaging script didn't rebuild it. i should have just removed both of the tarballs and had it regenerate everything once i fixed up the release nodes, which is what i just did. it's all happy now.
cheers,
-derek
Comment #4
jpulles commentedOk, thanks again and closed :-)