<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<font face="monospace">Hi Stefan,<br>
<br>
never mind. apt is just a wrapper around apt-get and aptitude for
convenience.<br>
So all holds true, one or the other way.<br>
<br>
Cheers,<br>
Matt<br>
<br>
</font><br>
<div class="moz-cite-prefix">Am 01.06.23 um 15:56 schrieb Stefan
Baur:<br>
</div>
<blockquote type="cite"
cite="mid:05dd529f-22a5-4ace-2dcb-d6a80de90d70@baur-itcs.de">Am
01.06.23 um 15:40 schrieb Buddy Butterfly:
<br>
<blockquote type="cite">Hi Stefan,
<br>
<br>
yes, you can trust me, that I always have a "clear" apt
installation with
<br>
<br>
apt update
<br>
apt dist-upgrade
<br>
</blockquote>
<br>
And here's the issue.
<br>
<br>
a) You should not run "apt dist-upgrade". Never. "dist-upgrade" is
not officially supported by "apt". (It is supported with
"apt-get", as far as I know.)
<br>
<br>
b) The proper command to use instead is "apt full-upgrade", but
...
<br>
<br>
c) You should always run "apt upgrade" before attempting a more
invasive command like "apt full-upgrade".
<br>
<br>
d) You should not use "-y" or a script containing the commands you
listed, unless you are willing to risk breakage AND have a proper
backup.
<br>
<br>
e) Read, Understand, and Think before you approve an update,
especially if it indicates package removals (which an "apt
upgrade" will never do, unlike an "apt full-upgrade").
<br>
<br>
<blockquote type="cite">apt autoremove --purge
<br>
apt autoclean
<br>
apt clean
<br>
</blockquote>
<br>
This is how I usually run manual updates on machines, usually
within a "screen" session when I'm logged in remotely, so a
natwork issue won't interrupt any dpkg-configure calls:
<br>
<br>
apt update
<br>
apt full-upgrade -d -y # see explanation below
<br>
apt upgrade
<br>
apt full-upgrade # optional step
<br>
apt autoremove --purge
<br>
apt clean
<br>
<br>
# Explanation: I want all packages to be available locally before
<br>
# starting the upgrade, so that any transient network failures
won't
<br>
# matter. It'll either fail at the download stage already, which
won't
<br>
# break anything, or it will be able to access all packages even
if
<br>
# the network fails inbetween.
<br>
<br>
Again, if any of these commands throw a warning/an error, do not
blindly continue.
<br>
<br>
IF, AND ONLY IF YOU HAVE A BACKUP THAT YOU HAVE VERIFIED TO BE
WORKING:
<br>
<br>
apt update && apt full-upgrade -d -y && \
<br>
apt upgrade -y && apt full-upgrade -y && \
<br>
apt autoremove --purge && apt clean
<br>
<br>
In your case, apt upgrade should have shown that it has some
packages it cannot upgrade due to unresolved dependencies, but
should have continued to work. The mess only starts after using
dist-upgrade/full-upgrade, because with that, you are actually
authorizing uninstalls. It is basically "Yes, do as I say!"'s
little brother.
<br>
<br>
Kind Regards,
<br>
Stefan Baur
<br>
<br>
</blockquote>
<br>
</body>
</html>