Re: confused about sudo apt-get vs kpkgkit
I'm baffled by why it would do that, it definitely shouldn't.
(From man apt-get):
I don't doubt your recollections, though. If it happens again the details might help to determine whether such behavior is a bug or caused by some extraordinary circumstances.
I usually use dist-upgrade as well. With larger upgrades (that include removal of packages) I sometimes run upgrade first to break the upgrade to smaller, more manageable chunks (it's easier to see which package upgrades want to remove/install packages once you get the other packages "out-the-way" by just "upgrading" first.
----
It's also worth noting that sometimes removing packages is really by design and necessary to upgrade [dist-upgrade]. But of course, like has been said on this thread before, you should always inspect what would get removed.
One should be extra cautious, if:
1. There would be more than a handful of packages removed when no obvious replacement packages are installed.
2. The system wants to remove something that looks/feels important to you.
3. An upgrade would remove more packages than would be installed/upgraded (upgrading 2 packages suggests removal of 4 packages).
In all these scenarios the removal of packages might actually be the "right" thing to do, but it's safer to hold the upgrade until you understand (or ask somenone who does) why those packages are marked for removal
Originally posted by steveriley
(From man apt-get):
upgrade is used to install the newest versions of all packages currently installed on the system from the sources enumerated in /etc/apt/sources.list. 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. New versions of currently installed packages that cannot be upgraded without changing the install status of another package will be left at their current version. An update must be performed first so that apt-get knows that new versions of packages are available.
Originally posted by steveriley
----
It's also worth noting that sometimes removing packages is really by design and necessary to upgrade [dist-upgrade]. But of course, like has been said on this thread before, you should always inspect what would get removed.
One should be extra cautious, if:
1. There would be more than a handful of packages removed when no obvious replacement packages are installed.
2. The system wants to remove something that looks/feels important to you.
3. An upgrade would remove more packages than would be installed/upgraded (upgrading 2 packages suggests removal of 4 packages).
In all these scenarios the removal of packages might actually be the "right" thing to do, but it's safer to hold the upgrade until you understand (or ask somenone who does) why those packages are marked for removal
Comment