Hi Marcus,
Thanks for your reply, but I'm afraid I still don't understand some of it. If the package is installed but the patch isn't, I thought I should see a green and white Z. What's the difference in these cases? When you say 'it will be gone', do you mean the patch will be installed?
The patch will be installed in this case (and this fact recorded). The problem here is that a patch might not just require some specific package versions, but also run scripts, display licenses etc.
Another aspect is why some patches are shown with a white triangle and white box with a black tick when the packages themselves have a black triangle with a green and white Z (e.g. krb5). Other patches for packages marked in this way are themselves marked with a white triangle and a green and white Z (e.g. python). What's the difference?
refresh, some packages have been installed that do not satisfy the patch.
Sorry, I don't understand this at all. What's refresh? How can I see what doesn't satisfy the patch (Check says all dependencies are OK)? How can I see what rule it is using to decide that something should be autoinstalled?
You can check the versions of the packages in the upper-right window. I guess one or more might not be fulfilled yet, while others are.
The final aspect is specific to gtk2. There is a patch for gtk2, which I have installed. Why can't I see a matching patch to gtk2-debuginfo? There's a version conflict. Am I misunderstanding something or is this a bug?
We do not ship updates for -debuginfo packages, you need to deinstall gtk2-debuginfo before updating.
Have I understood you correctly: As soon as there's an update to a package, it's no longer possible to debug it?
You can still debug it and the debugger will show a backtrace at least, its just that the debuginfo package cannot be used. (The reason we leave them out is just bandwith and diskspace issues.) Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org