Error installing module

Actually we hit that error on the initial porting. We could not really understand what was the real problem. AFAIK sdboyer work-around it just removing the table descriptions(completely weird, probably a mysql parse error?), but we would like to know if more if someone can really isolate the problem. We should not discard options like it could be one specific mysql version or something like that.

Sadly it seems like I was not really able to reproduce it, so comments more than welcome.

I have maybe a similar issue: the updates for this module fail. Already the first update #6102 returns the following error message:

DatabaseSchemaObjectDoesNotExistException: Das Feld <em class="placeholder"></em>.<em class="placeholder">versioncontrol_repositories</em> kann nicht hinzugefügt werden: Die Tabelle ist nicht vorhanden. in DatabaseSchema_mysql->addField() (Zeile 325 von /var/www/html/cm7/includes/database/mysql/schema.inc).

But the table is there!

mysql> show tables like '%versioncontrol%';
+-------------------------------------------------+
| Tables_in_drupal7 (%versioncontrol%)            |
+-------------------------------------------------+
| igs_intra_versioncontrol_account_status_strings |
| igs_intra_versioncontrol_account_status_users   |
| igs_intra_versioncontrol_accounts               |
| igs_intra_versioncontrol_cvs_accounts           |
| igs_intra_versioncontrol_cvs_repositories       |
| igs_intra_versioncontrol_item_revisions         |
| igs_intra_versioncontrol_labels                 |
| igs_intra_versioncontrol_operation_items        |
| igs_intra_versioncontrol_operation_labels       |
| igs_intra_versioncontrol_operations             |
| igs_intra_versioncontrol_repositories           |
| igs_intra_versioncontrol_repository_metadata    |
| igs_intra_versioncontrol_repository_urls        |
| igs_intra_versioncontrol_source_items           |
| igs_intra_versioncontrol_svn_repositories       |
+-------------------------------------------------+

I'm using a database prefix, maybe this causes problems here. And this site was ported from Drupal 6.

That's the first time that such database table updates do fail.

marking this postponed because it should be fixed with our "good enough" solution of removing all the description strings from the install file.

still about the weirdest damn error i've ever seen.

In the meanwhile I mananged to get update #6102 done. I just inserted the function into the D6 version of the module and run the update on my D6 site. So far so good.

But then the next error shows up:

versioncontrol module
Update #6300

    Failed: PDOException: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '))' at line 1: SELECT base.repo_id AS repo_id, base.name AS name, base.vcs AS vcs, base.root AS root, base.authorization_method AS authorization_method, base.updated AS updated, base.cron AS cron, base.init AS init, base.locked AS locked, base.data AS data, base.plugins AS plugins FROM {versioncontrol_repositories} base WHERE (base.vcs IN ()) ; Array ( ) in VersioncontrolEntityController->executeQuery() (Zeile 299 von /var/www/html/cm7/sites/all/modules/versioncontrol/includes/controllers.inc).

And here I have no idea to get this fixed. This update even does not run on my D6 site.

Second I am wondering about a comment regarding the 63xx updates:
"Update 6300 (from 6.x-2.0 to 6.x-3.0)"

Was there ever a version 3.0 of the Version Control module?

And what is the recommend migration path to migrate version "6.x-1.0-rc2" to D7? Should I just set the schema_version to 6999?

Finally I got all update hooks done.

I just updated all hooks from #6300 through #6322 to be D7 compatible. If someone is interested I can upload the 'patched' install file.

I'm also receiving this error on enable of the module. What I noticed in the error messages was the following text:

...depending on the version control systemÔÇÖs capabilities...

I've added a patch.

+1 for patch on #7

@nico.knaepen, thanks for the patch.

AFAIK I was no longer able to reproduce the problem, maybe mysql version, but in any case, this change is small enough, so it is now in upstream.

@marvil07 thanks for committing the patch.