CVS account problem?
hendler - January 15, 2008 - 20:56
| Project: | Drupal.org webmasters |
| Component: | User account problem |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
This may be a problem on my end: receiving a message on commits:
" pre-commit check failed"
I've run update.

#1
Might it be relevant that I've scheduled a release of "machine tags" ?
#2
we really need more info on this. What did you do?b
#3
THanks,
I'm simply trying to commit (via the CVS eclipse plugin), and I receive a message:
which is exactly:
The server reported an error while performing the "cvs commit" command.
SEMSEARCH: cvs commit: Pre-commit check failed
SEMSEARCH: cvs [commit aborted]: correct above errors first!
this message is the same for both projects I try to commit with:
Semantic Search, and Machine tags - where machine tags is the one I scheduled for release via the project page admin.
Beyond that I don't know how I can be more specific - but please let me know if you need something specific.
#4
To which module did you try to commit?
#5
THis commit message happens with both modules.
#6
All very strange. Did you use the checkout you are using now previously? If not I suggest to get a fresh checkout. I am not familiar with eclipse cvs but IMO all these interfaces only complicate things. did you consider cvs commandline?
#7
I'm guessing you checked out the workspace as anonymous@cvs.drupal.org. Either that, or you don't have CVS access to the right project(s).
Furthermore, either way, the CVS error message should be giving you more information. Eclipse must be silently dropping some of the error message text in its effort to be "user friendly" and "hide the ugly details". :(
#8
Note: please include a full link to the project nodes that you're trying to commit changes to. Saves us CVS admins the trouble of searching and trying to find them.
#9
working in IRC
hendlerman: Bdragon: I had run update first, before the commit. But that didn't work. (just tried again), and I am the only account holder on these modules...
[10:14pm] Bdragon: hendlerman: Then check what the CVS/Tag file reads in the checkout
...
hendlerman: Bdragon: in my root directory in CVS/tag is TDRUPAL-5
[10:18pm] Bdragon: Hmm, THAT's fine, it's the same in your module directories?
[10:19pm] hendlerman: in my other module there there is no tag, since it's head
[10:19pm] Bdragon: OK, that's fine as well
#10
My projects I am trying to commit to.
http://drupal.org/project/machine_tags
http://drupal.org/project/semantic_search
http://drupal.org/project/machine_tags has a release scheduled.
#11
in response to #7, I have them checked out as "hendler" and have had many successful commits.
As far as eclipse being the issue, it's possible. I am not familiar with the command line - so If I were to commit via command line perhaps there would be more error messages. I will try that and report here.
#12
perhaps my access was changed or denied because of the scheduled release?
cvs update: ignoring demo/modules/cck/po (CVS/Repository missing)
cvs update: ignoring demo/modules/cck/theme (CVS/Repository missing)
cvs update: ignoring demo/modules/coder/images (CVS/Entries missing)
cvs update: ignoring demo/modules/coder/includes (CVS/Entries missing)
cvs update: ignoring demo/modules/coder/scripts/coder_format (CVS/Entries missing)
cvs update: ignoring demo/modules/coder/tests (CVS/Entries missing)
? .DS_Store
? contrib/.DS_Store
? contrib/ARC2/.DS_Store
? contrib/SONIA/ext/stores/.DS_Store
? contrib/SONIA/ext/stores/sesame_resin/.DS_Store
? demo/.DS_Store
? demo/modules/.DS_Store
? demo/modules/cck/.DS_Store
? demo/modules/coder/.DS_Store
? demo/modules/date/.DS_Store
? demo/modules/email/.DS_Store
? demo/modules/link/.DS_Store
? demo/modules/views/.DS_Store
? demo/modules/views/modules/.DS_Store
? demo/modules/views/po/.DS_Store
? docs/.DS_Store
? js/.DS_Store
cvs update: Updating .
A LICENSE.txt
A README.txt
M semantic_search.module
M semantic_search_rpc.module
cvs update: Updating .settings
cvs update: Updating conf
M conf/semantic_search.constants.inc
cvs update: Updating contrib
cvs update: Updating contrib/ARC
cvs update: Updating contrib/ARC2
cvs update: Updating contrib/SONIA
M contrib/SONIA/sonia.includes.inc
cvs update: Updating contrib/SONIA/doc
cvs update: Updating contrib/SONIA/ext
cvs update: Updating contrib/SONIA/ext/cache
cvs update: Updating contrib/SONIA/ext/io
cvs update: Updating contrib/SONIA/ext/io/drupal
cvs update: Updating contrib/SONIA/ext/stores
cvs update: Updating contrib/SONIA/ext/stores/arc2
cvs update: Updating contrib/SONIA/ext/stores/arc_local
cvs update: Updating contrib/SONIA/ext/stores/sesame_resin
cvs update: Updating contrib/SONIA/ext/stores/sesame_rpc
cvs update: Updating css
cvs update: Updating demo
M demo/README.txt
cvs update: Updating demo/modules
M demo/modules/.cvsignore
cvs update: Updating demo/modules/cck
cvs update: Updating demo/modules/coder
cvs update: Updating demo/modules/coder/scripts
cvs update: Updating demo/modules/date
cvs update: Updating demo/modules/date/images
cvs update: Updating demo/modules/date/po
cvs update: Updating demo/modules/demo
A demo/modules/demo/demo.info
A demo/modules/demo/demo.install
A demo/modules/demo/demo.module
cvs update: Updating demo/modules/email
cvs update: Updating demo/modules/link
cvs update: Updating demo/modules/views
cvs update: Updating demo/modules/views/modules
cvs update: Updating demo/modules/views/po
cvs update: Updating demo/zend_framework
cvs update: Updating docs
M docs/INSTALL.txt
M docs/README.txt
M docs/SEMANTIC SEARCH - USER GUIDE.odt
cvs update: Updating html
cvs update: Updating includes
M includes/semantic_search.node_hooks.inc
M includes/semantic_search.search.inc
M includes/semantic_search.themes.inc
cvs update: Updating js
cvs update: Updating scripts
cvs update: Updating tests
This was an anonymous update.
then trying to commit via eclipse failed again, will try to commit via command line again: need to learn to do this via command line with credentials. (unless it's already cached somewhere....?)
#13
attaching my CVS settings in eclipse.
#14
pending machine tags release
http://drupal.org/node/210348
#15
dww: looks to be correct that eclipse suppresses all needed warnings:
the errors are suppressed: via command line....
** Access denied: this file is not allowed:
** contributions/modules/semantic_search/LICENSE.txt
** The only files allowed in contributions/profiles are .txt and .profile
** Packaged files (.gz, .tar, .tgz, and .zip) are not allowed anywhere.
** License files (LICENSE.txt) are not allowed, since everything committed
** to the Drupal CVS repository must be licensed under the GPL.
** Access denied: this file is not allowed:
** contributions/modules/machine_tags/LICENSE.txt
** The only files allowed in contributions/profiles are .txt and .profile
** Packaged files (.gz, .tar, .tgz, and .zip) are not allowed anywhere.
** License files (LICENSE.txt) are not allowed, since everything committed
** to the Drupal CVS repository must be licensed under the GPL.
semantic search committed properly. Trying to delete that file in machine_tags now.
Until I can commit machine tags and remove the LICSENSE.txt file, I'd like to keep the ticket open.
But... Thank you very much for jumping on this and providing guidance!
#16
now I appear to be stuck with:
$ cvs up
cvs update: Updating .
R LICENSE.txt
$cvs commit
** Access denied: this file is not allowed:
** contributions/modules/machine_tags/LICENSE.txt
** The only files allowed in contributions/profiles are .txt and .profile
** Packaged files (.gz, .tar, .tgz, and .zip) are not allowed anywhere.
** License files (LICENSE.txt) are not allowed, since everything committed
** to the Drupal CVS repository must be licensed under the GPL.
cvs commit: Pre-commit check failed
cvs [commit aborted]: correct above errors first!
Begins again....
#17
Nice to see that eclipse strikes again. My hatred of CVS GUIs continues to grow without bounds. ;)
I just forcibly removed LICENSE.txt from the machine_tags directory. All should be well...
#18
thanks!!!
Looks good from here. Again, much appreciated.
#19
sorry, setting to fixed again
#20
Automatically closed -- issue fixed for two weeks with no activity.