Am Montag, 14. Mai 2012, 23:41:55 schrieb phanisvara das:
i doubt it's really the zypper backend at fault. if that was the case, why does packagekit act up the same way in fedora?
excerpt from "TLWIR 37: Fedora 17 Takes Off" (http://beginlinux.com/blog/2012/05/tlwir-37-fedora-17-takes-off/ ):
Did you not read the thread? It was about a specific error message and as I suspected zypper patch showed the same error. Packagkitd dies after some time if nothing calls it again. Just to be clear, there are bugs in all apps, including packagkit and apper. Yet blaming apper by default (as it was done here and has become a common habit on forums by people like Carlos) is completely useless. It hinders bugfixing and it demotivates devs that are not at fault etc. The only useful approach is to help people debugging and that way find out where the bug is acutally at. That's why I asked to try zypper patch instead of zypper up in order to make sure it is actually a packagekit or apper bug. Sven -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org