On Tue, 15 May 2012 02:06:01 +0530, Sven Burmeister
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.
my my, aren't we touchy on this topic. i did not, at least did not mean to blame apper in particular. it's just that apper is the user-facing application in this case, and using it results very often in the same hangup that was described by the OP (basil c.) as the beginning of this thread. the same thing has been experienced by very many others, including myself. perhaps apper is the best application under the sun, but it does and must use other libraries, which also, on their own, are pretty good app.s. (actually, i can't say this about packagekit, since i'm only aware of it's existence n combination with apper & zypper libs, and that doesn't look good. but to give it the benefit of the doubt, i'll assume it does very many other things very well.) in the article i quoted above (you didn't read that, did you?) apper isn't even mentioned; only that packagekit starts with the system (fedora 17) and blocks the package management system, like apper does (in conjunction with others, and i don't know which one is to blame!) in openSUSE. of course it's not the same bug, it's a different distro. my uneducated guess would be that it's packagekit's fault; either by doing something wrong, or being so difficult to deal with that both fedora & OS dev.s don't get it right for some reason. i must admit that i'm not burning with desire to fix that bug. i can live very well without the whole triumvirat of apper/packagekit/zypp. i just remove those packages, and if others have similar problems, that's what i suggest. perhaps i can manage to include a disclaimer in the future, that it's not a loyal or helpful way of doing things... -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org