Just a quick note today from the CodeIgniter project - if you've been using their Subversion server to pull your latest copies of the framework down, they've made a change.

Our Subversion repositories have moved. Please update your repositories or check out new ones from the new location: http://svn.ellislab.com/CodeIgniter/trunk

The normal downloads (and archive files) are still available on the CodeIgniter download page.

On the Symfony project blog there's a recent post from <>Fabien Potencier about the popular framework's development and source moving to a new home - github.

As you might have noticed if you follow me on Twitter (which you should do as I make a lot of small announcements there), or if you monitor the Subversion activity closely, the Symfony 2 code is now hosted on Git. [...] So, from now on, all the development activity for Symfony 2 will take place on the new Git repository.

He briefly covers what git is and a resource (book) he used to help understand this recently popular version control system. If you don't want to learn a new version control system but still want to contribute back with the subversion knowledge you're already armed with, you can still use their svn mirror to get the latest releases.

On the Content with Style blog, there's a "quickie" you can drop into a subversion hook as a part of your check-in that will run the lint command on only the changed files (not your entire repository).

If you haven't done it in a hook already, here's the quick way to check all your changed files for syntax errors.

This sort of command would be the most useful in a pre-commit hook to ensure that everything passes correctly. Their example only looks for ".php" files, but can be modified easily if you happen to use ".html" or another custom extension for your pages too.

Mark Karpeles found a problem when he updated his Subversion install to the latest in the 1.6.x series - an XML error about opening the filesystem.

After some searches I found someone who had the same problem, and fixed it. Basically the problem is due to the SQLite version embed into PHP 5.2.x. PHP includes SQLite 3.3.7 while SVN will usually depend on 3.6.15 (or whatever you have on your system).

There's three solutions to the issue - disable PHP, update SQLite or create a new repository with the "-pre-1.6-compatible" flag to make it all play nicely together.

The PEAR blog has posted some handy instructions for those out there that want to get PEAR and PEAR2 checkouts working from the new Subversion repository (recently moved from CVS).

Now that pear2 is in svn.php.net, it is possible to do commits with multiple packages using a feature of subversion called "sparse checkouts." [...] Here is the version I used to set up pear and pear2 in a way that will allow committing to both pear and pear2 packages in a single commit.

Rasmus Lerdorf has written about the same thing for the main PHP side of things. All the commands you'll need are there to get things set up and working more efficiently.

If you're a fan of Planet-PHP (our fellow PHP news source) and have wanted to see how things run behind the scenes, you might want to check out this bit of information from Christian Stocker on where the source has ended up.

After Lukas asked me for the current Planet sources, I realized that I didn't really maintain the sources in the mentioned SVN repository anymore (for various reasons). So I decided to finally move them to GitHub. It makes much more sense there, since the most decent thing to do if you want to set up your own planet is to fork it and git (plus GitHub) makes that painlessly easy. Nevertheless I'm of course still interested in patches.

He warns that the code is a bit on the old side and that the framework its based on has officially been deprecated. If you're still interested, though, you can find (and clone) the application from its GitHub page.

Frederic Marand has pointed out a new subversion repository that's been set up for the documentation on the PHP-GTK project.

After recent complaints in the PHP-GTK mailing list, auroraeosrose mentioned mgdm has set up a SVN repository for the docs, to ease working on them. This new repository is available at http://svn.thefrozenfire.com/phpgtkdoc/

The trunk currently has repositories for the gtkdocs and the phpdoc application you can check out and use to generate and develop on the documentation locally.

Juozas Kaziukenas has a new post to his blog today looking at using Phing to keep files in sync on a shared hosting, FTP only kind of environment.

Today I was trying to use [Phing] in shared hosting server, but as you will see, Phing can't do a lot of it's functionality without direct access to server (over shh for example). [...] Things get worse, when you try to sync files in shared hosting environment, where only FTP is available. [...] Code in the hole some months ago posted solution which uses Net_FTP (FTP functionality wrapper) package to upload files to server. I decided to try given solution, so I modified it to download source code from SVN first and then upload them.

His Phing configuration sets up the application, defining the source directory, the files to push, the FTP connection to make and pushes the files over out of an svn export. He has a slightly different solution (no code/config for this one) that would grab the last revision value from the remote server and only push out the files have have changed since then.

In a recent post Fabien Potencier took a look at one method for getting metadata information from a subversion repository about the project(s) inside.

Last year, I deployed a new tool to manage symfony plugins. The first goal of this tool was to simplify the process of contributing new plugins. [...] The question I wanted to answer was quite simple: How many plugins were created per month before and after the change?

He uses a very handy option to modify the output of an "svn log" command - the "--xml" argument. This outputs the latest information (like author, date, paths and msg) for each of the log entries. This can then be thrown into a call to simple_xml_load_file and parsed down into the numbers he was looking for. He even generated a graph of the results as they coordinated with the different symfony releases.

In this new post Robert Basic expands on an older post about installing LAMP on a Ubuntu system by tossing Subversion (SVN) into the mix.

This post is a rewrite of one of my older posts, Ubuntu as a dev machine, but this time I'll explain also how to setup a basic SVN besides the LAMP. [...] Once again, I'm installing it under VirtualBox (VB).

He includes all of the apt-get commands you'll need as well as configuration options and commands to get your first project imported into subversion.