Based on that, your update-systems knows which packages can be upgraded.
If you wish to stay with a specific release branch, then you must specify the appropriate code name on the source line.
We currently use the following code names unifi3/unifi4/unifi5 but they are going to be obsoleted.
The [email protected] » aptitude --simulate -y -v safe-upgrade The following packages will be upgraded: ndiff nmap 2 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
This article provides a list of source files you'll need to create, or lines you can use in an existing file, if you wish to be able to install and update Uni Fi on your Debian or Ubuntu system via APT.
The system package manager, such as yum or apt, manages updates in this case in the same way as it does without Plesk.
Therefore, if there are other repositories available in the system, updates can be installed from them.
That is the most common method for package updates and installs for these OS. The stable, old stable and testing sources are considered floating, which means they can change at any time.
The repo structure should be permanent, but if there are any changes they will be pointed out both in the release posts, as well as this article. Typically there will be a post on the community announcing this.
To disable safe updates: Prohibiting Updates from Different Repositories To prohibit unsafe updates, you can hide the option Enable safe updates for system packages, which can be used to allow unsafe updates.