merging from an unrelated bzr project.

After converting my old svn repositories to bzr, I was left with a few other projects that had been in bzr all along that I wanted to integrate into the larger bzr collection. In this e-mail thread in one of the bzr mailing lists. I found a technique for doing this.

It says:

Currently, the way to do it is to set the base to 0 explicitly. E.g.
"bzr merge -r 0..-1 OTHER_BRANCH".

I'm such a bzr novice that I don't even know for sure exactly what this means but it seemed to work.

migration to bzr

For several years now, I've been using svn for VC on my personal files. When I upgraded my server to ubuntu gutsy, I started running into some trouble with svn. I could read repositories but was getting database errors when I tried to write to them. Rather than try to figure this out, it seemed like a good time to switch to bzr.

This ended up working pretty well. I used svn2bzr.py to convert the svn repos to bzr and now remote access works with bzr+ssh. I created a bzr user to manage the repos. At first I forgot to change the repository ownership to bzr so I had some permission problems but these went away upon correctly setting the ownership.

I ended up upgrading my server bzr version from 0.9.0 to 1.2 which seemed to make things run smoother. I'm not sure whether or not the problems that I was seeing were related to the permissions issue or the version though. On windows, I'm currently running 1.3

I still need to do a checksum on binary files to make sure that they came through the transition ok but so far everything seems fine.

Incidentally, I'm also using a root level bzr repo on the server to track changes to config files. So far so good.

installing ubuntu 7.10 ( gutsy) over the network

I have a machine that I've been using as a server for a couple of years. Unfortunately, it has a broken cdrom drive which means that I can't easily reinstall a new operating system. I *could* bite the bullet and get a new cdrom but I have not done this because it needs a laptop drive and I don't want to pay the extra expense, I'm a little concerned about compatibility and I am not sure how much trouble it is to swap out the drive.

In any case, this machine has been long overdue for a os upgrade. I have been running some old version of ubuntu (hoary?) and I wanted to start from scratch with gutsy. The important data is on a couple of partitions that I can leave untouched and I had some free space on the drive.

My first thought was to copy an iso to a usb key but this did not work because, to my surprise, the machine does not have a way to boot from usb.

So, I fell back on installing from the network. For several years now I've done this with varying degrees of success using this page as a reference.... and I'm happy to say it worked today.

However, it took me a couple of times to get it to work. I think I might have downloaded the wrong linux/initrd.gz/default files the first time around. It took me a few tries to figure out how to specify the paths to the files in the menu.lst file for grub (it ended up being by full pathname). It was essential to specify a desktop environment to install - I used vanilla ubuntu - without that things just didn't seem to work at all. I had to specify /dev/sda to install grub onto the mbr instead of /dev/hda like the example said.

All that is behind me now and things seem to be working just fine!

git vs bzr - further impressions

I find myself leaning towards bzr. I've been using git for a while now and the commands just seem less intuitive. For example. git-checkout with no arguments tells what items are deleted from a repository but git-checkout with an argument restores the argument if it is deleted. I'm not sure what git-checkout with an existing argument does.

bzr-svn

Somehow I got the idea that it would be cool to be able to checkout a sourceforge project using the bzr-svn plugin. It turns out that this plugin requires an old version of bzr (1.1) and an unreleased version of svn (1.5) or later. I don't mind the old version of bzr but I don't want to take the time to build the new svn so this will have to wait. Maybe I'll try git-svn .

windows permissions problem (solved)

Yesterday I discovered that users other than myself could not install new software on a shared computer. This was due to not being able to access the "Program Files" folder. The other users all had administrator status but that did not seem to be enough.

It turns out that there is a level of control in windows that only shows up when in safe mode (!). For some reason, only I had full access to the "Program Files" . After booting in safe mode I was able to add full control for the administrators group and this took care of the problem.

Without being in safe mode, I couldn't even diagnose the problem since user/group access settings were not visible. Is there a program that will let me view/edit these settings in normal mode?

I also am curious as to what program changed these settings? Perhaps coLinux/andLinux since these packages have to do some things at a pretty low level and they have the option for file sharing between linux/windows - that's just a guess though.

on second thought

On second thought another way to handle the c++ -> calc connection would be to use swig to enable python to call c++. This way the spreadsheet could be used to handle both input and output. So... the next experiment is to call python functionality from inside of calc.

And it turns out it's easy. Just put the python program into:
c:/Documents and Settings/dave/Application Data/OpenOffice.org2/user/Scripts/python
and it is available as a macro. Need to play with this a little to see if it really suits my needs.

Still need to see if I can get swig to work with the python that comes with open office.

This may be a problem. The swig documentation implies that you need version compatibility between the python executable and the swig code for swig to work.

Yes this is a problem. I can't yet even compile the swig examples because the python included with open office is not a complete developement environment. Or at least I can't find the Python.h include file needed to compile the swig examples.