Upgrade 2.5 to 2.6 and to 2.7,nothing works

Hi there, sorry you're having trouble. Your configurations should work (Ubuntu Lucid, RTAI, LinuxCNC 2.5, 2.6, and 2.7), so we just need to figure out where things went wrong and fix it.

How did you do the upgrade from 2.5 to 2.6? From 2.6 to 2.7?

Can you supply the output from the following commands, for debugging:

dpkg -l 'linuxcnc*'
dpkg --audit
debsums -c linuxcnc

Thanks!

I just installed LinuxCNC using the 2.5 Install Image (Ubuntu Lucid, RTAI, LinuxCNC 2.5), then upgraded to 2.6 using the instructions on the wiki , and verified that the sim/axis/axis config ran. I then upgraded to 2.7 using these instructions , and again ran that config, and everything went well.

So I think the packages are fine, and the install process works, and something else must have gone wrong with your upgrades, or something is special about your system that affects the upgrade.

Please install 2.6 and run those commands that I asked for earlier.

It's strange that the problem is in /usr/lib/python2.6/dist-packages/linuxcnc.so, since that's not one of the files that the linuxcnc debian package installs. Maybe at some point you built from source and then ran "make install"?

Try this:

dpkg -S /usr/lib/python2.6/dist-packages/linuxcnc.so
dpkg -S /usr/lib/pyshared/python2.6/linuxcnc.so

Are there any old emc packages around? Try "dpkg -l emc*".

There shouldn't be, they should have been automatically removed when you installed linuxcnc 2.5.

But in any case we know that no debian package claims the erroneous file that's causing all the trouble. I don't know where it came from, but you could try removing it by hand. There may be other stray files around that can cause similar problems later, if so you should consider doing a re-install to get rid of them all (but make sure you save/backup your configs and other personal files first).

Thanks for all your debugging attachments. They show that your system has the right packages installed, plus the mystery linuxcnc.so in the wrong place that's breaking your upgrade.

I ran "make install" in our 2.5 branch (with the -n flag, so it didnt actually copy anything), and it wanted to place linuxcnc.so in /usr/lib/python2.6/dist-packages, exactly where yours is. I think someone (maybe not you) ran "make install" at some point, and that's why upgrades are broken for you now.

I think your options are to try to remove the accidentally installed non-package files by hand, or wipe your system and reinstall. We are deep in dangerous territory now, but this shell script will run for a long time and then show all files in /usr that are not owned by any debian package on your system. You could try removing them all and see if that makes things better. I'd opt for a reinstall myself.

for F in $(find /usr -type f) ; do dpkg -S $F > /dev/null ; done