https://bugzilla.novell.com/show_bug.cgi?id=276494 sh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #4 from sh@novell.com 2007-05-30 04:03 MST ------- (In reply to comment #0)
If by chance you use the software-install module and select Packages > All packages > Update if newer version available, you are not notified that it also selected patches.
No, it doesn't. That function goes through all the packages in the libzypp pool and marks those for update that have newer versions than you have installed. It does not do anything with patches, patterns or other libzypp objects.
The latter would not be a problem, if those patches were handled as patches, yet if you install them and open YOU afterwards, they are still shown as available, instead of installed.
Of course. You installed the newer packages, but not the patch itself. A patch is just a container that holds together a number of packages. Technically, it's even a bit more complicated: A patch consists of zypp "atoms" which are meta-objects that only have dependencies on a package each. This is a helper construction to make sure you only get the updated package installed if you have a previous (older) version of that package installed. A patch also has an "installed" etc. state for dependencies: A service patch might require a number of patches to be installed, each of which has atoms that require certain minimum versions of packages to be installed, if that respective package is installed at all. If you then (accidentially or intentionally) try to install an older version of one of those packages, the dependencies of the corresponding patch will be violated, which in turn will violate the dependencies of the service pack. What you did with that "Update all packages" feature, however, is something different. You simply updated all the individual packages that you have installed to their respective latest versions. Some of that versions may come from update repositories; that's why you see update servers being accessed for package download. You did not, however, install any of the corresponding patches. This is what that feature explicitly does not do, does not attempt to do, does not promise to do, and is not supposed to do. It's something different.
Expected behaviour: Either do not install patches via software-install module, or handle them as YOU would, i.e. mark them as installed.
After using "Update all packages", you will see that all the corresponding patches have a checkmark icon in front of them in the "patches" view. That means that they are satisfied because all package versions they demand are already installed. You can simply mark those patches for installation. That will make the patch meta data to be marked as "installed" without further package download or installation (because the packages are all already up-to-date). Notice that this is not just cosmetic: If a patch contains a package that you don't have installed yet, you will get the latest version of that package (from the patch) if you later choose to install that package. This is what the patch enforces with its dependencies. Conclusion: You misunderstood what that feature is all about. -> INVALID -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.