How to reinstall mp-fremantle-pr? - maemo.org

Active Topics

How many of you still use N900 as main phone? (595)
to Community by deutch1976 - 13 hrs, 8 mins ago
Big news (7)
to OS2008 / Maemo 4 / Chinook - Diablo by endsormeans - 1 day, 22 hrs ago
Firefox with Leste (8)
to Maemo 7 / Leste by endsormeans - 1 day, 22 hrs ago
Which is the best N95? What software modifications could be made to it? (3)
to General by Kalatti - 4 days, 22 hrs ago
Installing CSSU Stable in year 2024 (2)
to Maemo 5 / Fremantle by teroyk - 5 days, 6 hrs ago
Porting apps to Leste (34)
to Maemo 7 / Leste by Arno_11 - 5 days, 15 hrs ago
more...

Page 1 of 4

Next >

Last »

Thread Tools

soeiro	2010-06-13 , 21:14
Posts: 292 \| Thanked: 131 times \| Joined on Dec 2009	#1

Hello

I was installing some apps from extras (no testing or devel enabled, tools also enabled) using apt-get instead of the app manager. Since it seemed go smoother (less load and less wait than app manager) I've decided try to install some updates too. So I did an apt-get dist-upgrade without paying too much attention.

After it was finished I realized mp-fremantle-pr was removed to solve some conflict. So, here are the questions:

1) How can I reinstall mp-fremantle-pr?
2) What is the real difference between regular app manager and apt-get? I thought that the only difference was that with apt-get one could see all packages...
3) If I can reinstall that package, sticking to apt-get upgrade (instead of dist-upgrade) will behave just as if I were to install upgrades using app manager?

Thanks.
PS. I would like to avoid another reflash, if possible.

__________________
Help improve N900, vote for:
Information about what the email client is doing
Find applications easily with tags for sub-menus
A better help system
Limit download of emails per connection type (don't fetch attachments)
A better use of internal flash

Last edited by soeiro; 2010-06-13 at 21:16. Reason: correct info

Quote & Reply |

Rob1n	2010-06-13 , 22:11
Posts: 3,617 \| Thanked: 2,412 times \| Joined on Nov 2009 @ Cambridge, UK	#2

Originally Posted by soeiro

1) How can I reinstall mp-fremantle-pr?

apt-get install mp-fremantle-*

Originally Posted by soeiro

2) What is the real difference between regular app manager and apt-get? I thought that the only difference was that with apt-get one could see all packages...

I'm not certain. Generally speaking, app manager only deals with the user visible packages (and not with libraries, etc). It also has a far more strict view on dependencies/conflicts and often refuses to install where apt-get is quite happy. I suspect it won't ever uninstall a package (unless you've specifically chosen the uninstall option), whereas apt-get will quite happily uninstall whatever packages are required to satisfy the install request you make.

Originally Posted by soeiro

3) If I can reinstall that package, sticking to apt-get upgrade (instead of dist-upgrade) will behave just as if I were to install upgrades using app manager?

apt-get upgrade will only update packages you already have installed, so it shouldn't cause any problems (I've not seen any anyway). The issues more frequently come with either "apt-get install" or (as you say) "apt-get dist-upgrade". In either case, it's just a matter of reading through the changes it's proposing and understanding the implications though.

Quote & Reply |

	breakd0wn	2010-06-14 , 01:31
	Posts: 96 \| Thanked: 35 times \| Joined on May 2010	#3

You can use apt-get -s to check 1st what it will do.

Quote & Reply |

soeiro	2010-06-14 , 18:36
Posts: 292 \| Thanked: 131 times \| Joined on Dec 2009	#4

Originally Posted by Rob1n

apt-get install mp-fremantle-*

I've tried that, but the system says that there are broken dependencies and then it exits.

I'm used to command line aptitude and its options to help solve broken dependencies (under Debian testing). However, I think I've downgraded packages just once, a long time ago, and it involved pinning some packages and some other voodoo.

Be the way it looks, a lot of QT libraries and bindings were installed and among them there might be the thing the conflicts with mp-fremantle-pr. I just don't know and can't find a way around it.

Any further ideas?

By the way, thanks for the info. I'll take care of using only apt-get upgrade for now on (I have to pay attention, because I'm just used to "aptitude full-upgrade" in Debian testing).

Quote & Reply |

Rob1n	2010-06-14 , 19:17
Posts: 3,617 \| Thanked: 2,412 times \| Joined on Nov 2009 @ Cambridge, UK	#5

Originally Posted by soeiro

I've tried that, but the system says that there are broken dependencies and then it exits.

Can you post the exact error? Does it mention what packages are causing issues, or does it just ask you to run "apt-get -f install"?

Quote & Reply |

	vitaminj	2010-06-14 , 20:30
	Posts: 405 \| Thanked: 961 times \| Joined on Dec 2009 @ London, UK	#6

I had a very similar problem - there was an updated version of hildon-initscripts in the tools repo that bust the mp- package when I did a dist-upgrade. I did an apt-cache policy hildon-initscripts to see the versions available, then rolled back using apt-get install hildon-initscripts=version.number I think. After that I was able to put back the mp- package (and simultaneously install pr1.2) with a normal apt-get install.

Quote & Reply |

The Following 2 Users Say Thank You to vitaminj For This Useful Post:
lore, YoDude

soeiro	2010-06-14 , 22:03
Posts: 292 \| Thanked: 131 times \| Joined on Dec 2009	#7

Originally Posted by Rob1n

Can you post the exact error? Does it mention what packages are causing issues, or does it just ask you to run "apt-get -f install"?

It was complaining about the version of hildon-initscripts to be installed being not compatible with mp-fremantle-generic-pr. Sorry for not posting it before, but I didn't have a connection for my N900 at the time I first posted. Thanks for helping out.

Turns out that hildon-initscripts that I had came from the tools repository.

Originally Posted by vitaminj

I had a very similar problem - there was an updated version of hildon-initscripts in the tools repo that bust the mp- package when I did a dist-upgrade. I did an apt-cache policy hildon-initscripts to see the versions available, then rolled back using apt-get install hildon-initscripts=version.number I think. After that I was able to put back the mp- package (and simultaneously install pr1.2) with a normal apt-get install.

Thanks very much for this. I thought I would have to dig how to pin down and downgrade everything, but there was no need. I just saw that my problem was exactly like yours and the solution worked. I had forgotten about "policy" and "=version"...