Hi,

I've asked a couple of days ago to unpublish some of my automatically created release nodes for the module "weather". I wanted to unpublish the nodes for some old branches, i.e. I don't see the need to generate a nightly tarball from the CVS version in those cases. Those releases are 4.3.x-1.x, 4.4.x-1.x, 4.5.x-1.x, and 4.7.x-1.x. However, they have appeared again. I guess that the old release nodes are still unpublished, but the script just checked if there are such releases available -- and if not, automatically creates them. Am I right in thinking that I have now two release nodes for each of the above mentioned branches, one published, one unpublished?

Regards,
Tobias

Comments

dww’s picture

Assigned: Unassigned » dww

whoops. ;)

ugh, this is sort of complicated, since the existing workflow is that when you first add a new release node, it's unpublished. so, the script can't just filter on only published nodes, since that would make it not really have any work to do at all. ;)

however, i suppose it should filter for release nodes that are a) unpublished but b) already have a filename. in that case, it shouldn't re-generate the tarball and re-publish the release (currently, it always tries to set the published bit on a node when it's done, to handle the common case of publishing the node for the first time).

luckily, this is a small fix. stay tuned.

p.s. no, you don't have duplicate nodes. it just re-published the same nodes i had already unpublished.

dww’s picture

Status: Active » Needs review
StatusFileSize
new2.3 KB
dww’s picture

Status: Needs review » Fixed

natrak said this is RTBC, so i committed to DRUPAL-4-7--2 as revision 1.1.2.17.

dww’s picture

i just re-unpublished all the contrib releases that were 4.5.x or older (per thread on infrastructure email list)
and also "weather 4.7.x-1.x" by request...

toddy’s picture

Great, thanks a lot for your fast response and the special treatment for my 4.7.x-1.x release ... ;-)

Anonymous’s picture

Status: Fixed » Closed (fixed)