SYSTEMS AND METHODS FOR AUTOMATIC UPGRADE AND DOWNGRADE IN PACKAGE UPDATE OPERATIONS
First Claim
1. A method for managing package updates, comprising:
- receiving a request to perform a distribution upgrade from an installed distribution comprising a first set of software packages installed on a client machine to a target distribution comprising a second set of software packages;
determining a version of each package in the second set of software packages;
determining a most-current version for each package in the second set of software packages;
determining whether when the most-current version of each package in the second set of software packages is a match for an upgrade for the version in the second set of packages;
upgrading each package in the first set of packages to the version of the corresponding package in the second set of packages when the version in the second set of packages is a match for an upgrade for the most-current version; and
downgrading the version of each package in the second set of packages to a most-current version when the version in the second set of packages is not a match for an upgrade of the most-current version.
1 Assignment
0 Petitions
Accused Products
Abstract
Embodiments relate to systems and methods for automatic upgrade and downgrade in package update operations. A physical or virtual client machine can host an installed software distribution including a set of installed software packages, such as an operating system, application, and/or other software. A package manager on the client can manage the set of installed packages, and report the installed distribution including version and component packages to one or more package servers. When a distribution upgrade is initiated, the package manager and/or other distribution logic can analyze the target distribution, to determine whether each package in the target distribution represents the most-current version of each component package. Packages which represent the most-current can be installed. Packages which do not represent the most-current version, e.g. due to slippage in vendor updates or versions, can be substituted with a most-current version automatically retrieved from a software repository or other source.
54 Citations
20 Claims
-
1. A method for managing package updates, comprising:
-
receiving a request to perform a distribution upgrade from an installed distribution comprising a first set of software packages installed on a client machine to a target distribution comprising a second set of software packages; determining a version of each package in the second set of software packages; determining a most-current version for each package in the second set of software packages; determining whether when the most-current version of each package in the second set of software packages is a match for an upgrade for the version in the second set of packages; upgrading each package in the first set of packages to the version of the corresponding package in the second set of packages when the version in the second set of packages is a match for an upgrade for the most-current version; and downgrading the version of each package in the second set of packages to a most-current version when the version in the second set of packages is not a match for an upgrade of the most-current version. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. A system for managing package updates performed on a client machine, comprising:
-
an interface to a data store storing a set of software distributions; and a processor, configured to communicate with the data store via the interface and to— receive a request to perform a distribution upgrade from an installed distribution comprising a first set of software packages installed on the client machine to a target distribution comprising a second set of software packages stored in the data store, determine a version of each package in the second set of software packages, determine a most-current version for each package in the second set of software packages, determine whether when the most-current version of each package in the second set of software packages is a match for an upgrade for the version in the second set of packages, upgrade each package in the first set of packages to the version of the corresponding package in the second set of packages when the version in the second set of packages is match for an upgrade for the most-current version, and downgrade the version of each package in the second set of packages to a most-current version when the version in the second set of packages is not a match for an upgrade of the most-current version. - View Dependent Claims (13, 14, 15, 16, 17, 18, 19, 20)
-
Specification