On Wed, Nov 16, 2011 at 12:19 PM, Vincent Untz
The second bug (from what I read) refers to the issue of packagekit not honoring the signal to close, when asked to by yast.
It's honoring it, but it can't honor it when it's busy. That's why speeding up the zypp backend is the right thing to do.
That's not a fix, it happened to me rather often that the zypp backend blocks for a very long time because of firewall issues. In order to go around those issues, I have to change the repos, but I can't do that with the zypp backend locking the repo. Chicken and egg. The only solution I had was killing packagekit, (kill -9) freeing the lock on the repo. No corruption happened since it was only waiting on a dead connection. The backend should be able to abort a network operation when asked to abort. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org