Message: previous - next
Month: December 2011

Re: [trinity-users] KDE-Trinity 3.5.13 hung my machine

From: David Hare <davidahare@...>
Date: Mon, 19 Dec 2011 16:10:03 +0000
On 19/12/11 15:43, Ken Heard wrote:
> Hash: SHA1
> Mag. Dr. Nikolaus Klepp wrote:
>> when you upgraded within TDE, then the upgrade was not complete. redo the
>> upgrade from a text console (<ctrl>+<alt>+<f1>).
> Aha!  I remembered when I did the first upgrade by running command
> "apt-get upgrade" 225 packages were upgraded, but 47 packages were kept
> back.  Of these 47, all but four had either "trinity" or "kde" in its
> name.  The other four were "lib" packages.  At the time the first 225
> packages were upgraded, it occurred to me that I should as a second step
> upgrade the other 47 packages; but I neglected to do so.
> Now, taking my cue from Mag. Dr. Klepp did so.  Once again I ran the
> command "apt-get upgrade".  Apt-get however identified the 47 packages
> but refused to upgrade them.
> I next decided to try the "aptitude upgrade" command instead.  The
> response from that command stated that 46 of the 47 packages that
> apt-get refused to install aptitude would install.  I addition, aptitude
> would remove nine more packages and install five new ones.  It
> recommended one more package but would not install it.
> After all of the forgoing was finished, ctrl-alt-F7 revealed the login
> screen ready for entry of user name and password.  I logged on and was
> able to open Konqueror without difficulty.  (There was however a problem
> with Konqueror which will be the subject of another post to the list.)
> I am consequently quite curious as to why aptitude would install the
> missing packages; whereas apt-get would not.  I could not find anything
> in the release notes or the Debian installation instructions to indicate
> that in upgrading to 3.5.13 aptitude should be used instead of apt-get.
>   I initially used apt-get because the release notes and instructions for
> the Lenny to Squeeze upgrade specifically recommended using apt-get
> instead of aptitude.
> Ken Heard, Toronto, Canada

I don't use aptitude myself so can't help much with that.

What I do know is, <apt-get upgrade> is a "safe upgrade" command which 
upgrades only those packages (or libs) which do not affect other 
packages. That's where you got into difficulty.

What you needed was actually <apt-get dist-upgrade> (see <man apt-get>)

For everyday use, you should stick to one or the other as their 
package-tracking databases may differ