https://bugzilla.suse.com/show_bug.cgi?id=1230631 https://bugzilla.suse.com/show_bug.cgi?id=1230631#c5 --- Comment #5 from Michael Andres <ma@suse.com> --- (In reply to Martin Wilck from comment #4)
I had to kill the zypper main process with SIGKILL. However afterwards the transaction seems to have been complete, and libzypp was at 17.35.8. Maybe the issue was caused by updating libzypp during the transaction?
Well, updating libzypp is quite common. Zypper(22706) and zypp-rpm(23678, which runs the rpm transaction) are both up and running, so an update of libzypp on disk should not bother them. At this point zypp-rpm is driving the transaction and zypper(libzypp) is just watching, receiving the progress and rpm output via the pipes. Killing Zypper(22706) closed the pipes. This released zypp-rpm(23678) and it continued silently. A running rpm transaction is not interrupted by killing zypper. This is expected and explains why libzypp was updated at the end. Might be a protobuf issue, but if it's reproducible with libzypp-17.35., we need to dig deeper. -- You are receiving this mail because: You are on the CC list for the bug.