Apt get why are packages held back




















What is Pyenv? Pyenv is a fantastic tool for installing and managing multiple Python versions. It enables a developer to quickly gain access to newer versions of Python and keeps the system clean and free of unnecessary package bloat. It also offers the ability to quickly switch from one version of Python to another, as well as specify the version of Python a given project uses and can automatically switch to that version.

This tutorial covers how to install pyenv on Ubuntu What is a Dependency? A dependency is defined as a file, component, or software package that a program needs to work correctly. Almost every software package we install depends on another piece of code or software to work as expected. It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search. Here it says:.

This can be resolved by either using aptitude to choose these packages for installation or by trying apt install package. In some stackexchange answers on related questions like this one it says that running apt-get dist-upgrade can be dangerous during a upgrade when packages have been held back and instead recommend using other more cautious methods than just running apt-get dist-upgrade or apt full-upgrade even though this old page at debian-administration.

When I run sudo apt upgrade not in the official guide instead of sudo apt-get upgrade it only shows 1 package having unmet dependencies. This should resolve the conditions which resulted in the packages being held back with the minimal upgrade, notably by removing obsolete packages and installing new dependencies: apt-get upgrade only upgrades already-installed packages, whereas apt full-upgrade will remove and add packages as necessary as well as upgrading packages.

Sign up to join this community. The best answers are voted up and rise to the top. You could install those packages manually with the command:. This command will not remove any packages unless they are unused and will install the kept-back software.

Either route you take, you'll get those kept-back packages installed. Which route you take will depend on if you want to add more software into the mix or do things manually.

Since this is Linux, you always have choices. In this case, make the one that makes the most sense to you. You don't want to miss our tips, tutorials, and commentary on the Linux OS and open source applications.

Delivered Tuesdays. Burathar Burathar 1 2 2 bronze badges. To move forward, edit you question and make the case mre. They are probably kept-back after an algorithm in apt deemed it wouldn't upgrade them, not because they are in the hold state. An easy method to know why they were kept back is to try to upgrade them explictly. Once you know the reason, maybe you can devise something about it with ansible. VladimirBotka The issue is that it's not something that can be reproduced easily, because there has to be some dependency or so, that causes apt to not upgrade the packages in certain situations.

B I was afraid that that would be the answer, haha. We'll probably have to do some more manual work to check out each different held back package separately then. And it is a bit unfortunate that the python-apt package that ansible uses, does not behave in the same way as apt itself.

Show 1 more comment. Active Oldest Votes. The following packages will be upgraded: tmux 1 upgraded, 0 newly installed, 0 to remove and 68 not upgraded. Improve this answer. Vladimir Botka Vladimir Botka 2, 6 6 silver badges 15 15 bronze badges. The problem isn't about manually held back packages, it is about packages that are automatically held back by apt itself.



0コメント

  • 1000 / 1000