Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.We opened the project page for supersearch (http://www.drupal.org/project/supersearch) a few weeks ago (to get feedback on the demo), and tried to commit the first code yesterday. When we downloaded the CVS structure for the first time to a new Ubuntu install an error message that sounded vaguely like "Your newborn has disappeared" :) popped up. We created the directory and tried to commit and filed a request to package a new version. The version is not coming up, and View all releases shows this:
ERROR: /usr/bin/cvs -q export -r HEAD contributions/modules/supersearch failed with status 1
So, we need help; looks like the CVS directory just got cleaned off at some point.
Comments
Comment #1
avpadernoThe release page shows this error:
Looking at the modules repository, there isn't a directory supersearch. This seems a common error for who imports the CVS structure.
You can find useful information on http://drupal.org/node/84256.
Comment #2
MisterSpeed commentedKiamLaLuno: Thank you; I've read the document though and can't find a solution to my problem. In every prior case the server-side directory was created at the same time by drupal.org as my project page; the only difference this time is that we waited probably 2 or 3 weeks before posting code. I recreated the directory and committed it, but it now refuses all commits with:
ERROR: There are no CVS tags for this module that do not already have a release associated with them.
To create a release, you must first create either a new CVS tag on one of the existing branches for this project, or you must add a new CVS branch.
Once you have created a tag or branch that should be used for your new release, try pressing the Retry link to continue.
---
There are no releases, so this shouldn't happen. Can you just reset all releases and directories so that I can start fresh ?
Comment #3
avpadernoActually, there was the release node that you tried to create after the CVS import.
I removed it, and now you should be able to create it again.
The error you get is probably caused by the fact your local CVS files have a tag that doesn't existing in Drupal.org CVS for your project.
Comment #4
MisterSpeed commentedVery much appreciated, thank you. I will try to commit the code again later today and update the ticket accordingly.
Comment #5
MisterSpeed commentedYikes. It clearly shows a commit, but the packager returns this on View All releases:
Packaging error messages
* ERROR: contributions/modules/supersearch does not exist after cvs export -r HEAD
I know my way around source-control systems (though I am much more at ease with SVN and SourceSafe), and I just don't know what is going on, nor can I see what is on the server side (so it is a basically a guessing game for me). I'm also worried that we are making people wait and loosing their goodwill. Would you have the exact steps that i need to do to make sure that all works well ?
Comment #6
avpadernoI can report you the link for the CVS reference guide for module maintainers, that is the guide I use: http://drupal.org/handbook/cvs/quickstart.
I normally use Komodo IDE to commit code to Drupal.org CVS, but I use the command line to create the directory in CVS, and commit the first version of the files; after that, I do all the following commits from Komodo IDE (with the exception of when I add new files).
If you want, I can make the first commit for you.
Comment #7
webernet commentedThere's nothing in CVS:
http://drupal.org/project/cvs/612440
http://drupalcode.org/viewvc/drupal/contributions/modules/supersearch/
Comment #8
dave reidYeah, you haven't actually committed any files to CVS. You obviously know how to do it (you've committed files to supercron).
Comment #9
MisterSpeed commentedYup, of course. When I do issue the cvs commits here they seem to complete fine. I will try again in verbose mode (or with a network sniffer if that fails too) when I'm back on the dev machine later this weekend.
Comment #10
MisterSpeed commentedGoing nuts with this; after 2 weeks and a bunch of updates, I still commit, network sniffs still see a commit going through, yet nothing happens on the server side. I'll link a .zip from the module page. Could somebody pls. upload it ? My hunch is that once it's up, checking it out, commits and patching should work.
Comment #11
avpadernoI am not allowed to access the directory where the file is contained; otherwise, I would be willing to upload it for you.
Comment #12
dww@63reasons: You keep committing to the root of the contributions repository:
http://drupalcode.org/viewvc/drupal/contributions/supersearch.module
Not to the location where you've told your project page your code lives:
http://drupalcode.org/viewvc/drupal/contributions/modules/supersearch/su...
Therein lies you're confusion and problem.
We periodically remove all the junk people import into the wrong place. Sadly, there's no good way to lock down the
cvs importcommand to prevent people from getting this wrong.Please try again using the right directory, and everything will work.
Comment #13
dave reidI had absolutely no problems committing the files to the proper directory using the instructions at http://drupal.org/node/612440/cvs-instructions/HEAD, so something wasn't followed correctly. Removed the mis-committed files from the root /contributions directory.