>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #232441. --> Reported by: [mlncn](https://www.drupal.org/user/64383) >>> <p>I apologize for the extreme messiness of this support request, but I just can't figure out what's going wrong. It's a just-committed module, so if there are steps to starting fresh (without starting a new project with a new name), that would be just fine, but I can't check out the project in a way that allows me to commit to it!</p> <p><a href="http://drupal.org/node/231951/release">http://drupal.org/node/231951/release</a></p> <p>Is giving me this error message:</p> <blockquote><p>Packaging error messages</p> <p> * ERROR: contributions/modules/term_message does not exist after cvs export -r HEAD</p></blockquote> <p>A potentially related error message I'm getting in cvs on the command line is that "cvs tag: nothing known about" my module, term_message.</p> <p>And the below error: </p> <blockquote><pre>Ebony-II:modules ben$ cd term_message/<br>Ebony-II:term_message ben$ cvs status<br>? .DS_Store<br>? term_message.info<br>? term_message.install<br>? term_message.module<br>cvs status: Examining .<br>Ebony-II:term_message ben$ cvs commit -m "added code to implement missing admin functionality"<br>cvs commit: Examining .<br>Ebony-II:term_message ben$ cvs add *<br>cvs add: cannot add special file `CVS'; skipping<br>cvs add: scheduling file `term_message.info' for addition on branch `HEAD'<br>cvs add: scheduling file `term_message.install' for addition on branch `HEAD'<br>cvs add: scheduling file `term_message.module' for addition on branch `HEAD'<br>cvs add: use `cvs commit' to add these files permanently<br>Ebony-II:term_message ben$ cvs commit -m "added code to implement missing admin functionality"<br>cvs commit: Examining .<br>? .DS_Store<br>** ERROR: Your commit is using a 'Sticky tag' which corresponds to<br>** a branch which is not valid in this CVS repository. If this<br>** commit were to proceed, you would create an invalid branch:<br>** HEAD<br>** <br>** See http://drupal.org/node/198469 for more information.<br>cvs commit: Pre-commit check failed<br>cvs [commit aborted]: correct above errors first!<br>Ebony-II:term_message ben$ cvs tag -b DRUPAL-5--1<br>? .DS_Store<br>cvs tag: nothing known about term_message.info<br>cvs tag: nothing known about term_message.install<br>cvs tag: nothing known about term_message.module<br>cvs [tag aborted]: correct the above errors first!<br>Ebony-II:term_message ben$ cvs update<br>? .DS_Store<br>cvs update: Updating .<br>A term_message.info<br>A term_message.install<br>A term_message.module<br>Ebony-II:term_message ben$ cvs tag -b DRUPAL-5--1<br>? .DS_Store<br>cvs tag: nothing known about term_message.info<br>cvs tag: nothing known about term_message.install<br>cvs tag: nothing known about term_message.module<br>cvs [tag aborted]: correct the above errors first!<br>Ebony-II:term_message ben$ </pre></blockquote> <p>This problem also <a href="http://drupal.org/node/73507#comment-425966">showed up for Dries</a>, and while no one had an answer at that time, my understanding is that he was able to continue on to be a productive contributor to the Drupal community ;-)</p> <p>How do I start fresh with a CVS checkout?</p> <p>Tried setting a new root:</p> <pre>Ebony-II:~ ben$ cd '/RCS/agaric/agaric-modules/'<br>Ebony-II:agaric-modules ben$ export CVSROOT=:pserver:agaric@cvs.drupal.org:/cvs/drupal-contrib<br>Ebony-II:agaric-modules ben$ cvs login<br>Logging in to :pserver:agaric@cvs.drupal.org:2401/cvs/drupal-contrib<br>CVS password: </pre><p>Reference:<br> <a href="http://nicksergeant.com/blog/2007/12/19/painless-drupal-revision-control-with-cvs-and-subversion/">http://nicksergeant.com/blog/2007/12/19/painless-drupal-revision-control-with-cvs-and-subversion/</a></p> <p>Report-back to:<br> <a href="http://codepoets.co.uk/drupal-through-cvs">http://codepoets.co.uk/drupal-through-cvs</a><br> <a href="http://agaricdesign.com/committing-a-project-to-drupals-cvs">http://agaricdesign.com/committing-a-project-to-drupals-cvs</a></p> <p>Though the task at hand is maintaining a contributed module that Agaric provides to the Drupal community by making available on Drupal.org -- this is not about deploying a Drupal site, yet.</p> <p>Trial:</p> <pre>Ebony-II:agaric-modules ben$ cvs -d:pserver:agaric@cvs.drupal.org:/cvs/drupal-contrib checkout -d cmt -r HEAD contributions/modules/cmt<br>cvs checkout: Updating cmt<br>U cmt/CHANGELOG.txt<br>U cmt/LICENSE.txt<br>U cmt/NOTES.txt<br>U cmt/README.txt<br>U cmt/cmt.css<br>U cmt/cmt.info<br>U cmt/cmt.install<br>U cmt/cmt.may_prove_useful<br>U cmt/cmt.module<br>U cmt/cmt_admin.inc<br>U cmt/default_thresholds.inc<br>cvs checkout: Updating cmt/js<br>U cmt/js/cmt_terms_node_view.js<br>Ebony-II:agaric-modules ben$ cvs commit -m "better installation message"<br>cvs commit: Examining cmt<br>cvs commit: Examining cmt/js</pre><p>That was successful.</p> <p>Error:</p> <pre>Ebony-II:agaric-modules ben$ cvs -d:pserver:agaric@cvs.drupal.org:/cvs/drupal-contrib checkout -d term_message -r HEAD contributions/modules/term_message<br>cvs checkout: Updating term_message<br>Ebony-II:agaric-modules ben$ ls -la</pre><p> [term_message is NOT there]</p> <p>Help?</p>