Maemo upgrades to multiboot packages prevents boot to Nitdroid and in some cases Maemo

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Install Nitdroid as per auto-installer instructions on wiki: 
http://wiki.nitdroid.com/index.php?title=N900-Autoinstaller (as per ~20 Aug 
2010) - note: at time - it was necessary to manually add extras-devel and 
testing in order to install package nitdroid-installer.
2.After successful install and boot to Nitdroid, returning to Maemo user finds 
package upgrades to multiboot* packages available.
3.Unsuspecting installs upgrades which are actually from Maemo 
(extras-devel/testing) which replace needed multiboot packages from Nitdriod.

What is the expected output? What do you see instead?
Expected result is Nitdroid versions of multiboot packages are preferred, but 
Maemo version prevail.

What is your device, RootFS and kernel versions?
Linux Nokia-N900 2.6.28.10power40 #1 

Please provide any additional information below.
It appears Maemo doesn't have apt-pinning configured/installed - alternative 
method of preventing Nitdroid multiboot packages being removed:
Rename packages and add conflict with Maemo packages involved?
Configure apt-pinning?
Auto add/remove extras-devel/testing apt-repos in sources.lst file during 
auto-install script?

See forum thread:
http://forum.nitdroid.com/index.php?topic=98.0

Original issue reported on code.google.com by [email protected] on 23 Aug 2010 at 10:48

[GoogleCodeExporter]

3.Unsuspecting installs upgrades which are actually from Maemo 
(extras-devel/testing) which replace needed multiboot packages from Nitdriod.

Should have read:

3.Unsuspecting *user* installs upgrades which are actually from Maemo 
(extras-devel/testing) which replace needed multiboot packages from Nitdriod.

Original comment by [email protected] on 23 Aug 2010 at 11:07