Abstract: An administrator system can generate a version identifier for a computing system based on the software packages installed on a computing system. The administrator system can utilize the version identifier to determine if software package updates will install properly on a computing system. When the computing system request an update to a software package, the administrator system can generate a version identifier for the software package, as installed on the computing system and to be updated. The administrator system can compare the generated version identifier to a test version identifier. The test version identifier can be a version identifier generated for a version of an exemplary software package known to properly install the update. Once compared, the administrator system can notify the user of the computing system of the comparison, for example, if the version identifier and the test version identifier are different indicating potential problems in the update.

Abstract: Embodiments relate to systems and methods for systems and methods for initiating software repairs in conjunction with software package updates. A physical or virtual client machine can host a set of installed software packages, including operating system, application, and/or other software. A package manager tracks the set of installed packages and updates available for the installed set. A notification tool, in conjunction with the package manager, can monitor the user's selection of package update options, and compare those updates to a diagnostic database, current state of the client machine, or other resources. Based on those determinations, the notification tool can generate one or more potential software repair actions to correct or avoid potential conflicts, faults, or other conditions that may arise due to, or may surround, the prospective package update.

Abstract: Embodiments relate to systems and methods for diagnostic notification via a package update manager. A physical or virtual client machine can host a set of installed software packages, including operating system, application, and/or other software. A package manager tracks the set of installed packages and updates available for the installed set. A notification tool, in conjunction with the package manager, can monitor the user's selection of package update options, and compare those updates to a diagnostic database and/or current state of the client machine. Based on those determinations, the notification tool can generate notifications to the user advising them of potential conflicts, faults, or other conditions that may arise due to, or may surround, the prospective package update. The notification can permit the user to continue or terminate selected updates, and the notification tool can re-analyze any potential faults after an update is completed.

Abstract: Embodiments relate to systems and methods for generating and storing translation information as package metadata. A physical or virtual client machine can host a set of installed software packages, including operating system, application, and/or other software. A package manager tracks the set of installed packages and language resources available for the installed set. The package manager can host or access a set of package attributes which include language specifications which indicates a language that should be used for search, display, and/or other activities. The language specifications be used to link to remote a remote repository storing various language metadata, including translations of source text. The resulting translated descriptions of source text from applications or other objects can be received and locally stored as translation information on the client machine. Translations can be periodically generated and/or updated.

Abstract: An administrator system can generate a version identifier for a computing system based on the software packages installed on a computing system. The version identifier can represent the software packages installed on the computing system. The administrator system can utilize the version identifier to manage a network of computing systems. The administrator system can compare the version identifiers of the computing system to verify that the computing system have the same software packages installed. Likewise, the administrator system can compare the version identifiers of the computing system to a test version identifier.

Abstract: An administrator system can generate a version identifier for a computing system based on the software packages installed on a computing system. The version identifier can represent the software packages installed on the computing system. The administrator system can identify the software packages installed on a computing system and data specific to the software packages. The administrator system can apply a hash function to the specific data to generate hashed data. Then, the administrator system can concentrate the hashed data to generate the version identifier.

Abstract: An administrator system can generate a version identifier for a computing system based on the software packages installed on a computing system. The version identifier can represent the software packages installed on the computing system. The administrator system can utilize the version identifier to manage a network of computing systems. The administrator system can compare the version identifiers of the computing system to verify that the computing system have the same software packages installed. Likewise, the administrator system can compare the version identifiers of the computing system to a test version identifier.

Abstract: A security tool can access a tagging tool and the history generated by the tagging tool in order to identify potential threats and analyze the identified threats. When a potential threat is detected or an actual threat is identified, the security tool can request the history of actions from the tagging tool corresponding to the threat. The security tool can compare the potential or actual threat with the history of any action recorded by the tagging tool in order to classify a potential threat as an actual threat or determine the source or cause of an actual threat.

Abstract: An administrator system can utilize a history generated by a tagging tool to determine the current configuration of computing systems. The administrator system can utilize the current configuration to verify that the computing systems have been configured properly and verify, over time, that the computing systems maintain the desired configuration. The administrator system can compare the current configuration with the desired configuration for the computing systems.

Abstract: In order to track actions performed by a package manager or a configuration management system, a computing system can be configured to include a tagging tool. The tagging tool can be configured to cooperate with the package manager and the configuration management system in order to determine and generate a history of the actions performed by the package manager and the configuration management system. The history can include a description of the actions, the reasons why the actions were performed, and a list and description of the software programs, files, and software libraries that are affected by the actions.

Abstract: In order to track actions performed by a package manager, a computing system can be configured to include a tagging tool. The tagging tool can be configured to cooperate with the package manager in order to determine and generate a history of the actions performed by the package manager. The history can include a description of the actions, the reasons why the actions were performed, and a list and description of the software programs, files, and software libraries that are affected by the actions.