I use this set in aptitude*, but in apt-get* it's exactly the same: sudo aptitude update && \ sudo aptitude safe-upgrade && \ sudo aptitude full-upgrade && \ # sudo aptitude clean Note the difference between safe-upgrade (upgrade in old versions) and full-upgrade (dist-upgrade in old version). safe-upgrade upgrades all packages which won't interfere with other packages, while full-upgrade will upgrade all packages, even if it requires removing (or "changing the name" of) third packages. * Please have a look at this link so you can use the gret libapt even better: <a href="http://www.debian-administration.org/articles/462">http://www.debian-administration.org/articles/462</a> Regards <div>2008/2/28, Paul Lemmons <<a href="mailto:paul@lemmons.name">paul@lemmons.name</a>>:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Not really a big deal but it has made me curious. When I: "apt-get update;apt-get upgrade" I see the following: Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: kaffeine miro 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Now I suspect that there is some dependent piece of software that would break if this update was applied and apt is just protecting me (an I am actually quite happy about that). The questions is how do I see what is causing the hangup? -- kubuntu-users mailing list <a href="mailto:kubuntu-users@lists.ubuntu.com">kubuntu-users@lists.ubuntu.com</a> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/kubuntu-users">https://lists.ubuntu.com/mailman/listinfo/kubuntu-users</a> </blockquote></div>