Comment # 3 on bug 1020117 from
Hi Stefan!  I think you may have misunderstood some aspects of my report.

(In reply to Stefan Hundhammer from comment #1)
> You are describing the behaviour in the package selector. That view
> intentionally does not show disabled repositories

My report isn't about disabled repositories; it is about *enabled* repositories
that (for whatever reason) failed to refresh.  Most people don't disable such
repositories right away, since it's not uncommon for the refresh to fail due to
transient network or server problems.

> because the subsequent
> behaviour would be confusing: If disabled repos were listed there and the
> user would click on such a disabled repo, what should happen?

But I already suggested exactly what should happen:  it should show installed
packages from that repository, but hide the uninstalled ones.  I think this is
much less confusing and much more consistent than simply hiding both installed
and uninstalled packages for that repository.

(In reply to Stefan Hundhammer from comment #2)
> P.S. To see what packages you have on your system that are no longer part of
> any active repository, select a view that shows all (installed) packages,
> such as "installation summary" (and select only "installed" packages on the
> left side), then sort the package list by version numbers

This isn't a full workaround, since I still can't see which packages came from
which repository without selecting each one individually and examining it. 
(And it's not unheard of for multiple repositories to go AWOL at the same time.
 In the last few weeks both the Java and LibreOffice Factory repositories were
moved.)  The only full workaround I'm aware of, as mentioned in my report, is
to use zypper from the command line.


You are receiving this mail because: