On 23/01/14 20:51, Bob Bernstein wrote:
A thread about dist-upgrade has me confused. In my experience I have only ever run 'apt-get dist-upgrade' when I wanted to move from one release to the next, say, from squeeze to wheezy. Similarly, if I wanted to insure I had the latest versions of packages already installed (and any/all security fixes) I have run 'apt-get update' followed immediately by 'apt-get upgrade.' But the thread currently underway about dist-upgrade suggests that users are running it rather routinely, and not at all necessarily to move from one release to the next. Can someone please point out what I am missing? Thanks,
From "man apt-get"
upgrade
(...)Packages currently installed with new
versions available are retrieved and upgraded; under no
circumstances are currently installed packages removed, or packages
not already installed retrieved and installed.
dist-upgrade
(...)The dist-upgrade
command may therefore remove some packages. The
When for instance a new version of an already installed package depends on a previously not installed library, then "apt-get update" cannot update this pkg. You need "dist-upgrade" for that job.
Just happened on my SID system: shotwell got upgraded to version 0.14.1-3b1, which now depends on (among others) libgphoto2-6, whereas the previous version depended on libgphoto2-2. Libphoto2-6 could not have been installed using "upgrade" (it's a new package rather than a new version of an already installed pkg)
HTH -- Klaus