On Sun, Jan 08, 2012 at 11:47:52AM +0100, Andreas Schwab wrote: > Carlos Martín Nieto <cmn@xxxxxxxx> writes: > > On Sat, Jan 07, 2012 at 09:25:27PM -0800, Abscissa wrote: > >> Well that's strange, it finished "upgrading", but now git is still just > >> reporting 1.7.0.4, which is *exactly* the same version it said before. The > >> git-svn package should already be up-to-date because I just installed it > >> today. So I don't know what's up with that. > > > > Nothing odd about that. apt-get upgrade means "upgrade my system". If > > you want to get a newer version of package X, you do apt-get install X > > and it will install the latest version of that package. > > If apt-get upgrade doesn't get you a newer version then apt-get install > won't help you either. No, this is true only if none of packages involved uses a new library (including new sonames). "apt-get upgrade" is forbidden to add or remove packages, and thus will skip upgrades that need a new dependency. The message at the end will mention "## not upgraded" though. "apt-get install X" or "apt-get dist-upgrade" have no such restrictions. -- 1KB // Yo momma uses IPv4!
Attachment:
signature.asc
Description: Digital signature