Skip to main content

Issues migrating from RCS to subversion (svn)

Just a note, I'm still in the process of doing this...
We decided to switch to a better way of doing SCM (Software Configuration Management) now that we've a major release and more and more people are starting to fiddle (aka mess) with scripts and files.

We decided to use Subversion from CollabNet, as a natural successor to CVS. It could also provide corporate support, if needed, and has a nice SourceForge version with web-based GUI and all kinds of handy features. Also, our RCS repository seems to import well into Subversion. Bazaar and Mercurial also seemed to fit, but somehow I thought I would have a much harder time explaining them to the people working with it.

The note, while using cvs2svn to import RCS into SVN (using cvs2svn -s /var/svn/repositories/rcs_import --existing-svnrepos --use-rcs RCS), I ran into an error: "svn: Expected version '3' of repository; found version '5'". This seems to be due to a schema change between subversion versions... I'm running a patched OEL 4u5 and that gives me:

[root@server ~]# svnversion --version
svnversion, version 1.1.4 (r13838)


Update: Turns out I had subversion installed twice. Once from Oracle Linux and once from CollabNet. Updating your $PATH is important to determine the version you use. OEL is at 1.1.x unless you run OEL 5.x which has subversion 1.4+. Collabnet, naturally, uses the latest SVN version 1.4.x. I was converting using the latest version cvs2svn (schema 5) and trying to import it into SVN repositories created using Collabnet (schema 5) but using the svnadmin from OEL (schema 3). Hence the error...

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Preventing PuTTY timeouts

Just found a great tip to prevent timeouts of PuTTY sessions. I'm fine with timeouts by the host, but in our case the firewall kills sessions after 30 minutes of inactivity... When using PuTTY to ssh to your Linux/Unix servers, be sure to use the feature to send NULL packets to prevent a timeout. I've set it to once every 900 seconds, i.e. 15 minutes... See screenshot on the right.
1 comment
Read more

Removing VGs or LVs from LVM

While are many excellent tutorials about creating and using LVM on Linux, not may show you how you can remove disks from LVM Volume Groups (VG) and reclaim storage or how to remove a Logical Volume (LV) from your LVM set-up. Here is what I did: Use -t to TEST ANY LVM action first! We are going to release 1 TB from LVM. The Volume group was extended with 1 TB storage to serve as a cheap NFS/CIFS file server when setting up our data center. It is now deprecated and replaced by a NAS so it's no longer needed. 1) check LVM; note the four 256 GB LUNs [root@server ~]# pvscan -v Wiping cache of LVM-capable devices Wiping internal VG cache Walking through all physical volumes PV /dev/sdb1 VG vgdata lvm2 [50.00 GB / 0 free] PV /dev/sdc1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdd1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sde1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdf1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdg ...
Post a Comment
Read more

Dell Linux - OMSA Hardware Monitoring

Just getting started using Dell's OpenManage Server Administrator (OMSA) on our Oracle Linux platform. There are some confusing instructions going around so it's not immediately clear what to do, hence my blogging here. :) There is a site on Dell - Hardware Monitoring , as well as a wiki with instruction on how to setup their OMSA tooling using yum or up2date. [update]My first update for their instructions: be sure your server has Internet access, as most servers will use a proxy or so. use export http_proxy=http://yourproxy.example.com:port to configure it just for the session, and setup up2date to use an HTTP proxy by editing the settings in /etc/sysconfig/rhn/up2date .
2 comments
Read more