Content Management Filter. Both versions have the correct sticky tags in my CVS.

The 5.x-1.5 release (http://drupal.org/node/525102) somehow has 6.x code in it. I checked my commits and they specify DRUPAL-5. I do see that the -dev release is rolling off HEAD, which I need to change (I don't like using HEAD).

What have I done wrong, and what do I do to get it straightened out?

Comments

nancydru’s picture

BTW, both versions were also done from check outs.

avpaderno’s picture

From what I can see, it seems somebody has manually added the information that the packaging script normally add.

This is the content of the .info file as appears from the CVS repository:

; $Id: cmf.info,v 1.2.2.3 2008/12/03 18:43:45 nunoveloso18 Exp $
name = "Content management filter"
description = "This module adds an easier way for administrators to filter the content on a Drupal site for administration purposes."
package = "Administration"
core = 6.x
; Information added by drupal.org packaging script on 2008-10-17
version = "6.x-1.1"
core = "6.x"
project = "cmf"
datestamp = "1224252903"


; Information added by drupal.org packaging script on 2008-12-04
version = "6.x-1.x-dev"
core = "6.x"
project = "cmf"
datestamp = "1228348974"

This is the content of the same file as found in the tarball archive for version 5.x-1.5:

; $Id: cmf.info,v 1.2.2.4 2009/03/12 12:39:19 nunoveloso18 Exp $
name = "Content management filter"
description = "This module adds an easier way for administrators to filter the content on a Drupal site for administration purposes."
package = "Administration"
core = 6.x
; Information added by drupal.org packaging script on 2008-10-17
version = "6.x-1.1"
core = "6.x"
project = "cmf"
datestamp = "1224252903"


; Information added by drupal.org packaging script on 2008-12-04
version = "6.x-1.x-dev"
core = "6.x"
project = "cmf"
datestamp = "1228348974"


; Information added by drupal.org packaging script on 2009-07-20
version = "5.x-1.5"
project = "cmf"
datestamp = "1248099031"

The packaging script adds the correct information for the Drupal 5 branch.

webernet’s picture

http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/cmf/cmf.inf...

It appears that the DRUPAL-5--1-5 tag is on the DRUPAL-6--1 branch.

You'll need to create a DRUPAL-5--1-6 tag is on the correct branch and make a new release. Once that's done, the problem release can be unpublished.

avpaderno’s picture

That is true: the code is tagged for both the Drupal 5, and Drupal 6 versions.

CVS Tags: DRUPAL-5--1-5, DRUPAL-6--1-5, DRUPAL-6--1-6, DRUPAL-6--1-7 
nancydru’s picture

Status: Active » Fixed

Thanks, I think it is fixed now. I also cleaned up the .info file for 6.x.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

avpaderno’s picture

Title: I have a messed up release. » I have a messed up release