When svn up does not work (WordPress subversion)
Today WordPress 2.3.3. was released as an urgent security update to the last version.
I wanted to update my install by making use of my subversion install:
so as usually I’d go on with opening PuTTy and logging into my server.
From sh I’d enter
svn upThis for some reason did not fetch all files and no real update was carried out. Any idea why? I have no guess.
So what I did was:
svn sw http://svn.automattic.com/wordpress/tags/2.3.3/More to type, but luckily this does update everything. Still an annoyance that svn up did not work.
I’m getting the same problem. The odd thing is I have one blog that updates to betas with “svn up” and one blog that doesn’t. I read on another site that it could have to do with permissions, but I checked and changed the permissions to be what they should, but the site still won’t update with “svn up”; I have to do as you’ve shown with the “sw” command instead. Annoying.
it’s a pain in the arse I know :/
You have to use the sw command because your svn is tied to a particular branch. For instance, at the time you posted, your blog’s svn was set to 2.3.3 and you will need to keep switching to stay updated. “svn update” only updates your stuff to the branch that you’re on. You /could/ sw to wordpress’s trunk, but then you risk breakage and difficulties (in exchange for earlier access to new features).
@Jeremy: thanks a lot for your detailed comment! I do now understand why I have to use svn sw .. , still it is annoying :) Using the bleeding edge release is one possibility, as stated by you, however this comes at certain caveats…
There’s a happy medium:
svn sw http://automattic.com/wordpress/branches/2.5/ .Today that would give you v2.5.2 alpha. And the only svn sw you’d have to do is when the 2.6 branch is ready enough for you.
@Jonathan: thanks for the hint, I will definitely bash that into putty later on!