Comment # 4 on bug 1175926 from David Diaz

(In reply to macias - from comment #3)
> Packman is just popular repo, "Packman is down" is the same as saying
> "Packman is offline" or "Packman server does not respond", something like
> this. I don't know the exact reason.

I knew about Packman ;) But I wanted to clarify the "is down" part because the
error shown in my screenshot in that situation.


> 
> As for your screenshot -- it is OK, but you taken it too late :-).
> 

:)

>  I.e. you
> taken it when Yast2 already _stopped_ because repository is not available.

During my tests, this alert was prompted quite fast. That's the reason why I
didn't understand your suggestion.

> 
> And I am talking (sorry I was not clear about that) about _progress_ -- when
> Yast still struggles/tries to reach the repo.
> 
> The moment Yast is done with repo X and goes to repo Y it should switch
> progress to "Y 0%". Currently it is not the case, it finishes with X with "X
> 100%" (ok), then switches to work with Y with progress still "X 100%" (not
> ok), it struggles because Y is down, and then you see the outcome as
> presented in the screenshot (I mean the progress bar in the background, not
> the error popup). So the visual switch with progress happens, but it should
> be sooner. IMHO.

I see. Let's wait for the Ladislav thoughts until go ahead processing the bug
report.

Thanks a lot, Macias.