7/25/2023 0 Comments Sudo apt get upgrade vs updateIf the package update was kept back for a reason unrelated to phasing, apt may be forced to remove packages in order to complete your request, which could then cause problems elsewhere. If you want to apt upgrade a package, you should first carefully examine the proposed changes that apt would make before you proceed. You’re unlikely to break your machine by doing this – as long as the package is being held back due to update phasing. While you can technically get around phased updates by running apt install on individual held back packages, it’s not recommended. Can I apt upgrade the individual packages? (and should I?) You will still temporarily get the “held back packages” message, but your machine will be more protected from updates that might otherwise break it – and once the packages are ready to be safely installed on your system, they will no longer be held back. If that doesn’t sound like something you want, leave phased updates on (this is the default). It will get rid of the “held back packages” in apt message, though. ![]() Be warned, though – if an update is broken, you will almost always be in the first set of people to get it (i.e., you’re basically volunteering yourself as a guinea pig for the early update releases!). If you just want to avoid any notices about packages being held back during apt updates, and you’re willing to be one of the first people to get updates whenever they’re released, you can turn off phased updates. That depends on how stable you need your system to be. ![]() It should be mentioned here that security updates are never phased. The phasing system makes it so that different sets of users are chosen to be the first to get the updates, so that there isn’t one group of unlucky people who always get potentially broken updates soon after release. In other words, it directly benefits our users by increasing the safety, stability and reliability of Ubuntu. ![]() It gives us the opportunity to hold back the update until the bugs are fixed. Update phasing makes it much easier for us to detect serious breakages early on – before they have a chance to cause problems for the majority of our users. This can obviously cause problems for our users, and used to be the norm before we phased updates through apt. Why is Ubuntu doing this?Īlthough updates are thoroughly tested before they get released at all, sometimes bugs can be hidden well enough to escape our attention and make it into a release – especially in highly specific use cases that we didn’t know we needed to test. Once the update has been deemed safe for release, you will receive the update automatically. The good news is, you don’t need to do anything about the “packages kept back” message – you can safely ignore it. As the update proves to be stable, it is provided to an ever-increasing number of users until everyone has received it (i.e., when the update is “fully phased”). Initially, the update is provided only to a small subset of Ubuntu machines. Phased updates are software updates that are rolled out in stages, rather than being provided to everyone at the same time. However, it has become a much more common occurrence due to something called “phased updates”. If you’ve ever used combinations of packages from different releases or third party repos, you may be familiar with this message already. ![]() (Names of held back packages listed here)Ġ upgraded, 0 newly installed, 0 to remove and not upgraded. The following packages have been kept back: You may have noticed recently that updating your system with apt upgrade sometimes produces a weird message about packages being kept back…like this one: Reading package lists. Multi-node configuration with Docker-Composeĭistributed Replicated Block Device (DRBD)
0 Comments
Leave a Reply. |