View Single Post
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#7
Originally Posted by mikecomputing View Post
Why on earth should this happen cause you're doing dist-upgrade?
Because dist-upgrade specifically tells apt to ignore safety and upgrade everything possible, removing any obsoleted/conflicting packages.

Originally Posted by mikecomputing View Post
And also isn't fastappmanager talking directly to apt-get if I remember right?
It is, but it's only doing install/remove/upgrade so apt should handle conflicts safely.

Originally Posted by mikecomputing View Post
I have done this plenty of times when upgrade linux desktops so I dont see why this even should happen in this case, only reason for it to happen is if there is a PR1.3 pending or similar. Or if I do apt-get --purge remove hildon-desktop or similar.
With most linux distributions, the repository only deals with a single version of the OS, so all updated packages are "safe" within the scope of that version (and dist-upgrade should do no more than upgrade). In order to update versions, you need to change the repository used, then use dist-upgrade. With the Nokia repositories, the single repository is used for all versions, and updated packages will only normally get pulled in when the master package (mp-fremantle-???-pr) is updated. New versions of packages seem to be uploaded in between though, and using dist-upgrade will cause these to get pulled in, dropping out the conflicting core packages.
 

The Following 2 Users Say Thank You to Rob1n For This Useful Post: