Linked by Thom Holwerda on Sun 9th Aug 2009 20:49 UTC
Thread beginning with comment 377818
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
If anything, the table shows that the upgrade process is still faulty. Probably because of all the pointless versions, complex licensing and the registry.
I'd say personally that the purpose of the registry is to ensure that a Windows application can't simply be copied (as a set of files in a folder) from one computer to another.
In doing this job, the registry necessarily gets in the way when trying to do an OS in-place upgrade. The upgraded OS will in effect "look like" a new computer to an installed application.
All of these types of problems arise due to the business method of selling binary-only copies of applications.
I would probably do:
- keep /etc/ and /home (and maybe some other dirs I cared about)
- dpkg --get-selections
- do a new install of 64-bit the same version with and install the needed packages with --set-selections
- put /etc/ and /home back
- then upgrade
or something like that, you get very close to an inplace upgrade from 32-bit to 64-bit.






Member since:
2005-07-06
Ubuntu cannot do in place upgrades from 32bit to 64bit (Using the normal upgrade routes).
The best way would be to leave the home directory (Hopefully on a different partition), Install the 64bit version and the ia32-libs and then re-install the set a packages that were previously installed.
Upgrading from 9.04 x86 to 9.10 x86 or 9.04 AMD64 to 9.10 AMD64 is usually a simple process. Anecdotally, I did not face any issue upgrading from 8.04 to 8.10 to 9.04, however attempting an in-place upgrade of Windows has lead to doing a fresh install each time.
(Nice blur effect Thom)
If anything, the table shows that the upgrade process is still faulty. Probably because of all the pointless versions, complex licensing and the registry.