How to update DRUPAL-4-7 from CVS?
Hi, I have a drupal install that I checked out of CVS some time ago, in the 4.7.3 timeframe, I believe. I'd like to update it to get something post 4.7.4. This is how I thought it should be done: cvs update -r DRUPAL-4-7 Or some variant close to that. But this causes a problem. The problem is that leaves me with duplicates of drupal core modules. For example in my modules directory, I get aggregator.module and aggregator/aggregator.module, block.module and block/block.module, and so on for all drupal modules which were once files but are now in their own directory. I was under the impression these modules which sit in their own directory are DRUPAL-5 modules. But if I understand CVS correctly (which is hard to do), those modules are also tagged DRUPAL-4-7. Is this an accident or am I doing something wrong on my end? Is there any way to update a DRUPAL-4-7 checkout without getting modules written for DRUPAL-5? Note that I am not using this command: cvs update -dPf -r DRUPAL-4-7 which I know would check out files added to DRUPAL-HEAD after DRUPAL-4-7. I thought the earlier command would be a safe way to upgrade a DRUPAL-4-7, but I think some files have been accidentally tagged as DRUPAL-4-7 when they should not be. Thanks, -Dave
On Nov 22, 2006, at 4:45 PM, Dave Cohen wrote:
Is this an accident or am I doing something wrong on my end? Is there any way to update a DRUPAL-4-7 checkout without getting modules written for DRUPAL-5?
there was a minor problem when the files were moved in CVS, but it should only effect date-based checkouts and updates. i mention it at the end of http://drupal.org/node/73507. one of these days i'm going to have a chance to fix this, but i've been saddled with work and honestly, haven't been getting too much help (with a few notable exceptions like merlin and webchick). the task of porting project* and cvslog.module to 5.x looms large, and i'm way behind at my day job...
I think some files have been accidentally tagged as DRUPAL-4-7 when they should not be.
i just double checked in the core repository, and none of the modules you mention in their own sub-directories have the DRUPAL-4-7 tag. most of us have been able to checkout/update a DRUPAL-4-7 workspace of core without any troubles. so, i'm guessing you've got something strange about your local setup (cvs client, sticky tag, sticky date, etc) that's causing your grief. try checking out a fresh copy: cvs -d[:pserver...] co -r DRUPAL-4-7 drupal you can also try doing that in place, on top of your existing workspace (backup first), and it should work like a cvs update. good luck, -derek
On Saturday 25 November 2006 01:12, Derek Wright wrote:
try checking out a fresh copy:
cvs -d[:pserver...] co -r DRUPAL-4-7 drupal
you can also try doing that in place, on top of your existing workspace (backup first), and it should work like a cvs update.
I've had this problem before, also, and wiping the directory and checking out a fresh copy did not help. By about the third update, I had a mixed setup of 4.7 and HEAD, with the update wanting to download every module and theme available. After several attempts to fix it, I finally just quit using CVS and went back to the "normal" way. FYI, I used this as my model, as it was the only thing that made sense to me at the time: http://www.lullabot.com/articles/cvs_quick_reference (It seems to have been updated since the last time I used it, 'cause I never did the diff thing. I concocted a different way of checking for changes.) -- Jason Flatt http://www.oadaeh.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 13; Cramer, 11; Travis, 9; Angela; Harry, 5; and William, 12:04 am, 12-29-2005) Linux User: http://www.sourcemage.org/ Drupal Fanatic: http://drupal.org/
participants (3)
-
Dave Cohen -
Derek Wright -
Jason Flatt