Closed (fixed)
Project:
Git on Drupal.org
Component:
Releases
Priority:
Major
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
18 Jul 2011 at 23:01 UTC
Updated:
10 Mar 2018 at 20:59 UTC
Jump to comment: Most recent, Most recent file
I've just received maintainership of RoleAssign (#1221396: Offering to maintain RoleAssign) and I found that there exists an odd HEAD/master release. I don't think this was created intentionally, nor has it ever been advertised, but it appears in the version selection list (http://drupal.org/node/add/project-issue/roleassign) — in fact it's even the default right now!
Please unpublish this release.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | roleassign-HEAD-release.png | 14.29 KB | salvis |
Comments
Comment #1
eliza411 commentedSome documentation for what to do here can be found http://drupal.org/node/1127732
It looks like the situation for RoleAssign is somewhat different, but it's a place to start.
Comment #2
salvisThank you for the pointer, eliza411, but I'm not asking for support here — I need to have a fubar node removed.
I've switched a bunch of -dev releases from the master branch to a new -dev branch according to the linked instructions, but as you write, this one is different (see the screen snapshot).
This is not a -dev release, it's a HEAD release (something that should not exist!), and to top it off, it shows not two packages, but four! It dates back to November 11, 2006. It was probably intended to be 5.x-1.x-dev, but there's a 5.x-1.x-dev, too. I'm getting ready to create a 7.x-1.x branch, but even if the UI would let me, I don't want to reuse a five-year-old borked release node for a new branch.
This release node seems to be the product of something that went wrong five years ago plus the Git Migration not being able to handle the unexpected form of that node and producing something that was never intended to exist.
I'm upping the priority because this is not the typical newbie cry-for-help but an issue that requires surgical intervention.
Comment #3
salvisThere's more trouble with this project:
in the following two release nodes
http://drupal.org/node/1225358
http://drupal.org/node/1225362
When I saved the first node, I found that the body text was somehow lost. Trying to recover my carefully crafted text, I hit the browser's Back button, and this apparently created the second node. Now they're both broken...
Comment #4
eliza411 commentedSorry, I had little time yesterday to respond and probably should have waited to say anything at all. My apologies.
I unpublished the HEAD release node, /node/96748.
I also removed the two nodes you posted in comment #3 above, neither of which had any text in the release notes so that you can try recreating a release.
I'm also assigning this to @sdboyer for review in case there are further problems.
Comment #5
salvisNo problem, thank you for your help, eliza411.
Removing the two release nodes listed in #3 has helped, the tag is available again and I'll try again.
However, unpublishing the bad node apparently isn't enough to get rid of the entry in the Version drop-down list: http://drupal.org/node/add/project-issue/roleassign (buglet?).
@sdboyer: Please remove the HEAD release node as soon as you don't need it anymore, or do whatever it takes to remove the 'master' entry from the Version drop-down list.
Comment #6
jacob.embree commentedMaster no longer appears in the version drop-down.
Comment #7
salvisThanks! :-)