http://bugzilla.suse.com/show_bug.cgi?id=1158478 http://bugzilla.suse.com/show_bug.cgi?id=1158478#c4 --- Comment #4 from William Brown <william.brown@suse.com> --- (In reply to Thorsten Kukuk from comment #3)
1. of course the log files do exist and are available in the system, they are not deleted. And if you want to have a shell, use the option to start a shell for debugging. Your claims in this regard are wrong.
But the shell won't be in the environment where the "error" happened, it will be a new snapshot yes?
2. zypper is giving you all informations to solve the problem. Instead of pasting the long output, you should have read it.
man zypper -> you try to install a package which does not exist, and zypper is even telling you that.
gdb suggested this command to install the debug info, so there is something gdb knows about these packages that doesn't line up when zypper attempts the download then. I'm just doing what the system is telling me here. For the record, I actually totally missed that error on multiple reads because there is so much information overload, and the error condition is listed *early* in the process, rather than being declared at the end. The error condition also doesn't include the important word "error" in it, making it further able to be overlooked. A better structure would be to move the relevant errors to the end of the output, near "Installation has completed with error." to help make the errors easier and accessible to spot - generally without "command" output I would expect anything "before" this point to be working for a package manager. IE: (54/54) Installing: liblzma5-debuginfo-5.2.4-4.3.x86_64 [............done] Installation has completed with error. ERROR: Package 'libsvrcore0-debuginfo-1.4.2.4~git0.c881f6ec0-82.1.x86_64' not found. ERROR: zypper install on /tmp/tmp.XXVSzekuha failed with exit code 104! Removing snapshot #8... Removing overlay directory /var/lib/overlay/8... transactional-update finished This output would have been much more helpful than the cryptic "script failed with error" code. So I think there are some genuine improvements to be made here for this. -- You are receiving this mail because: You are on the CC list for the bug.