update manager confused about available updates vs. up-to-date
Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
update manager confused about available updates vs. up-to-date
I've installed Linux Mint 11.
The update-manager shows in the notification area saying, "there are updates."
When I open the update-manager, it does its usualy dance but the status line says, "up to date". On the toolbar, the app shows
a checkmark to "install updates"
Nothing happens when I select the "install updates" item.
sudo apt-get update reports "Fetched ..."
sudo apt-get upgrade reports "O..." for everything
upgraded, installed, removed, etc.
sudo aptitude update reports "Fetched ..."
sudo aptitude upgrade reports "No packages ..."
How do I get things back in sync re TODO vs. DONE?
You can then find out what they upgradable packages are if any. They may have dependency problems which is why they won't be upgraded on a safe-upgrade.
ciao,
jdk
You can then find out what they upgradable packages are if any. They may have dependency problems which is why they won't be upgraded on a safe-upgrade.
ciao,
jdk
But, he never issued the safe-upgrade command.
I haven't used a Debian-based system for awhile, but it seems to me that it would be best to try:
But an aptitude upgrade will not install new dependencies, only update already installed packages.
An aptitude safe-upgrade, on the other hand, will install new dependencies.
Just pointing out a possible reason for a held-package.
Where do you see that, Andrew? I've looked at at man aptitude and aptitude --help and neither mentions an upgrade command but only safe or full upgrade. I know they changed the command from dist- to full- and upgrade to safe-upgrade. My understanding was both old commands still work but they prefer to you use the more current ones.
Anyway, If you have a reference, I'd like to see it. Thanks,
jdk
and found no reference to aptitude upgrade, only safe-upgrade and the fact that dist-upgrade is now full-upgrade.
It doesn't actually state what happens when you issue an upgrade.
Quote:
safe-upgrade
Upgrades installed packages to their most recent version. Installed
packages will not be removed unless they are unused (see the
section "Managing Automatically Installed Packages" in the aptitude
reference manual). Packages which are not currently installed may
be installed to resolve dependencies unless the --no-new-installs
command-line option is supplied.
If no <package>s are listed on the command line, aptitude will
attempt to upgrade every package that can be upgraded. Otherwise,
aptitude will attempt to upgrade only the packages which it is
instructed to upgrade. The <package>s can be extended with suffixes
in the same manner as arguments to aptitude install, so you can
also give additional instructions to aptitude here; for instance,
aptitude safe-upgrade bash dash- will attempt to upgrade the bash
package and remove the dash package.
It is sometimes necessary to remove one package in order to upgrade
another; this command is not able to upgrade packages in such
situations. Use the full-upgrade command to upgrade as many
packages as possible.
full-upgrade
Upgrades installed packages to their most recent version, removing
or installing packages as necessary. This command is less
conservative than safe-upgrade and thus more likely to perform
unwanted actions. However, it is capable of upgrading packages that
safe-upgrade cannot upgrade.
If no <package>s are listed on the command line, aptitude will
attempt to upgrade every package that can be upgraded. Otherwise,
aptitude will attempt to upgrade only the packages which it is
instructed to upgrade. The <package>s can be extended with suffixes
in the same manner as arguments to aptitude install, so you can
also give additional instructions to aptitude here; for instance,
aptitude full-upgrade bash dash- will attempt to upgrade the bash
package and remove the dash package.
Note
This command was originally named dist-upgrade for historical
reasons, and aptitude still recognizes dist-upgrade as a
synonym for full-upgrade.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.