Resolving "You are not allowed to delete or move tags"
| Project: | Drupal.org infrastructure |
| Component: | CVS |
| Category: | support request |
| Priority: | normal |
| Assigned: | aclight |
| Status: | closed |
Jump to:
I'm new to CVS, and have been having some problems. I'm trying to update my modules from DRUPAL-6--1-2-BETA1 to DRUPAL-6--1-2-BETA2, but CVS is telling me that BETA1 is revision 1.2, and BETA2 is revision 1.1. How this happened, I have no idea. But I believe that this revision problem is the reason that my module's page (http://drupal.org/project/innovationnews) still recomends beta1, even though beta2 is available.
I read around a little bit, and it seems that I need to do this (though I'm not certain, guidance would be greatly appreciated):
cvs update -F DRUPAL-6--1-2-BETA2
but when I try to do that, I get the "You are not allowed to delete or move tags" message. Could someone please change the tag, so I could preform the cvs update -F (that is, assuming cvs update -F is what I should do in this situation).
The project is /contributions/modules/innovationnews and the BETA2 release node is http://drupal.org/node/284546
Thanks alot!
#1
Sorry, but once a release has been rolled, correct or not, that release is static; it cannot be created again. This means you can't move the tag (the tarball will never be regenerated). The reason for this is that no one could tell WHICH beta2 they downloaded. And really, it's a good thing that there can't be multiple versions of beta2; it defeats the whole purpose of versioning.
The best you can do is make sure you have everything right and tag a new release.
The reason that your project recommends beta1 is that for whatever reason, beta2 is unpublished and inaccessible.
#2
It looks like the official release based on your DRUPAL-6--1-2-BETA2 tag was packaged successfully, as the file downloads and untars fine, and I don't see any error messages in the watchdog log of d.o for this release. However, for some reason the packaging script did not publish the release node when it was done packaging the release, and I can't figure out why that was. The release node itself was not tagged with the security fix term, so that wasn't the problem either.
I went ahead and published the release node, so on your project page BETA2 now shows up as the recommended release.
#3
Thank you so much for fixing that!
#4
Automatically closed -- issue fixed for two weeks with no activity.