Community SSU/Installation FAQ
(Formatting) |
m (Formatting) |
||
| Line 7: | Line 7: | ||
'''A:''' The best way to check out the source of the problem for this is to go into X Terminal and to use <code>apt-get</code> to install the package whilst Community SSU repository is enabled inside HAM: | '''A:''' The best way to check out the source of the problem for this is to go into X Terminal and to use <code>apt-get</code> to install the package whilst Community SSU repository is enabled inside HAM: | ||
| - | + | apt-get install ''package name that is causing the problem'' | |
| - | apt-get install ''package name that is causing the problem'' | + | |
| - | + | ||
In most cases, users with <code>modified-hildon-desktop</code> will have issues updating <code>hildon-desktop</code>. That is because <code>modified-hildon-desktop</code> overwrites schemes set out by the normal <code>hildon-desktop</code>. To alleviate this issue one needs to '''remove <code>modified-hildon-desktop</code>''' before retrying. | In most cases, users with <code>modified-hildon-desktop</code> will have issues updating <code>hildon-desktop</code>. That is because <code>modified-hildon-desktop</code> overwrites schemes set out by the normal <code>hildon-desktop</code>. To alleviate this issue one needs to '''remove <code>modified-hildon-desktop</code>''' before retrying. | ||
Revision as of 08:02, 26 January 2011
| Note: Most of the reasons why Maemo 5 Community SSU cannot be installed can be checked under the Problems tab when viewing the package in Application Manager. |
Q: I cannot install Maemo 5 Community SSU Package because of xxxxx package
A: The best way to check out the source of the problem for this is to go into X Terminal and to use apt-get to install the package whilst Community SSU repository is enabled inside HAM:
apt-get install package name that is causing the problem
In most cases, users with modified-hildon-desktop will have issues updating hildon-desktop. That is because modified-hildon-desktop overwrites schemes set out by the normal hildon-desktop. To alleviate this issue one needs to remove modified-hildon-desktop before retrying.