Comment # 6 on bug 1158478 from Thorsten Kukuk

(In reply to William Brown from comment #4)
> (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? 

If you call the same command again with the shell option, it will be the same
snapshot.

> > 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. 

And zypper is telling you, that a package you want to install does not exist
and quits with an error code.

> 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 end contains a clear statement: zypper exits with an error code and the
error code is mentioned. Exactly what you did request is printed at the end.

> So I think there are some genuine improvements to be made here for this.

If you read the the error code and what it means, you know for what you have to
search in the output.
The experience is: overlading the end with too much informatons does not help,
there will be exact the same bug reports as yours, as people don't read as they
claims it's too much informations.