By kpm on

Hi,

I have a multisite installation which was installed using cvs. I fell behind for a security upgrade so jumped from 6.10 to 6-12 by running cvs update -r DRUPAL-6-12 -dP followed by running ".../update.php" for that site. All went well, but when I ran ".../update.php" on the second site, I received the following notice:
system module can not be updated. Its schema version is 1004. Updates up to and including 1021 have been removed in this release. In order to update system module, you will first need to upgrade to the last version in which these updates were available.

I ran ".../update.php" on a third site and all went well. These were all originally version 6.x installs.

I was under the impression that minor versions can be skipped, but major version upgrades require a step through of each missed version... Anyway, I'm not sure why I get this on the second site upgrade attempt and not the first or third? They are both sharing the same code??

To resolve, do I have to downgrade from 6-12 to 6-11 (since I already ran cvs update -r DRUPAL-6-12 -dP) and then run the update.php on the one site throwing the error, then upgrade again, run update.php again? Will this cause any problems?

Thanks

⋅ Categories: Drupal 6.x

Comments

kpm’s picture

kpm commented

and got the following error:
user warning: Unknown column 'status' in 'where clause' query: SELECT * FROM files WHERE status = 0 and timestamp < 1243496871 in /var/www/drupal-6/modules/system/system.module on line 1226.

This doesn't make sense. Three sites, all fresh drupal 6.8 installs, upgraded before to 6.9, and then 6.10. Now, only two of them are able to upgrade, and one throws this error.