On 23-03-17, Greg Wooledge wrote:
> On Thu, Mar 23, 2017 at 02:42:20PM -0400, songbird wrote:
> > when you run:
> >
> > $ apt-get upgrade
> >
> > it will not add any new programs, but when you run:
> >
> > $ apt-get dist-upgrade
> >
> > it will tell you which are new of the updates it is
> > going to perform (if any).
>
> I strongly recommend using the half-documented -u option here:
>
> apt-get -u upgrade
>
> It's not in the man page, but it IS in the "apt-get -h" output.
>
> That way you'll have some warning of which services are going to be
> affected. If, for example, you see that your database server is
> going to be upgraded, and you know that this will impact your users,
> you may want to wait until a less busy time to do the upgrade, and
> shut down your database-client application(s), etc.
>
> This is also one of the reasons why unattended upgrades are not on
> by default.
>
Actually, it is in the man page of apt-get:
-u, --show-upgraded
Show upgraded packages; print out a list of all packages
that are
to be upgraded. Configuration Item:
APT::Get::Show-Upgraded.
Also, another option that could be more useful:
-s, --simulate, --just-print, --dry-run, --recon, --no-act
No action; perform a simulation of events that would occur based on
the current system state but do not actually change the system.
Locking will be disabled (Debug::NoLocking) so the system state
could change while apt-get is running. Simulations can also be
executed by non-root users which might not have read access to all
apt configuration distorting the simulation. A notice expressing
this warning is also shown by default for non-root users
(APT::Get::Show-User-Simulation-Note). Configuration Item:
APT::Get::Simulate.
Have fun :)
