Apologies, I'm a compleat CVS idiot and the more I try RTFM, the more confused I get. I'm really not even sure how to word my question(s).

My problem:
I was OK up until version 1.3 of my module. I then made several changes to the copy of my module in sites/all/modules/mymodule and tried to apply those to the copy in contributions/modules/mymodule by doing a diff and applying the resulting patch. When I went to commit my newly updated module, I got the following:

cvs commit: sticky tag `1.3' for file `autocreate.module' is not a branch
cvs [commit aborted]: correct above errors first!
cvs commit: saving log message in /tmp/cvst1dVNQ

Checked the status

[bilbo@localhost autocreate]$ cvs status -v autocreate.module 
===================================================================
File: autocreate.module Status: Locally Modified

   Working revision:    1.3
   Repository revision: 1.3     /cvs/drupal-contrib/contributions/modules/autocreate/autocreate.module,v
   Commit Identifier:   288e48edf39a4567
   Sticky Tag:          1.3
   Sticky Date:         (none)
   Sticky Options:      (none)

   Existing Tags:
        No Tags Exist

http://drupal.org/node/57516 says the first step in this case is to submit a support request, so here I am.

I've been thrashing around with this and did manage to get my new code in the repository somehow, because when I do a cvs update, the version I get is still 1.3, but the module includes the changes, with no new messages in my CVS history. I really need to be able to create a v1.4 and have a CVS message regarding the new features. I'm still in dev focusing on a 5.x version and I'm really not ready to start branching my code yet. I do intend to tag my next version as a "beta" release, but I don't have any other tagged releases yet.

First, though, I need to be able to commit again. I'm really not at all concerned with my "lost" version 1.3, I just need to get unstuck. Can you help?

many thanks,
Bill

Comments

sunset_bill’s picture

Greetings,

I'm still reading up on this and have a post on the Modules forum. From what I'm seeing, it looks like I'm pretty much stuck until a kindly CVS admin can get rid of that sticky tag on v1.3 of my module. If I'm asking in the wrong place, please let me know--It's my first module and I'd really hate to have it die in development just because I'm a -4 with CVS.

thanks,
Bill

sunset_bill’s picture

Priority: Normal » Critical

Please? I really am stuck here and according to what I see on drupal.org, this is the place to send a request for CVS help. I'd really like to move on with creating an actual release if I can get this sticky tag thing fixed. If not, my module is pretty much dead and should probably just be removed from the repository entirely so people don't try to use it.

thanks,
Bill

aclight’s picture

Priority: Critical » Normal

You didn't provide the exact command you used when you tried to commit your changes but got the "sticky tag is not a branch" error message, so I'm not exactly sure what's going on.

I suspect that you can solve your problem by checking out a clean copy of your module from CVS into a new directory, make the changes to your code, and then commit as follows:

cvs commit -m "Message goes here."

If that doesn't work, please provide all of the commands you're using to check out the module and attempt to commit your changes, since you might be using the wrong command somewhere.

vladsavitsky’s picture

I was used
cvs update -A
and than commit as usual.

dave reid’s picture

You need to have an actual branch checked out (like HEAD or DRUPAL-6--1, etc):
cvs update -RPdC -r DRUPAL-6--1

Once you are working on a CVS branch, you can commit.

avpaderno’s picture

Status: Active » Fixed

I am setting this as fixed, as it has gotten an answer.

Status: Fixed » Closed (fixed)

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

Component: CVS » Other