Frank-Michael Fischer <fmfischer(a)gmx.net> writes:
The reason why I am assuming it's libzypp's
fault is: when I filed the
bug it was for the Zen component, then Nat Budin changed the component
to libzypp and connected this bug with bug 176301. This bug I am not
supposed to view. So it's fair to guess there is something rotten in
the state of libzypp. And we should not participate, just sit and wait.
Why is everybody thinking there's something rotten going on if a bug
The bug is "Bug 176301 - Overview bug for performance issues regarding
zypp, zlm, NCC" and starts with:
We have identified some bugs which all have some influence to the performance
NONE of this is a blocker for itself, but alltogether results in the
performance we face now.
I opened this bug with severity blocker to keep track of all the issues.
If we could fix some/most of the related bugs, we could downgrade this one to
critical or even major.
Currently I am aware of #155591, #163186, #169719, #175880, #174887
If any one is aware of further bugs related to perfomarnce add the to the
dependency tree of this one.
And the developers add any bugreport that they thing is performance
related. Nothing more. The initial report was against SLES10 which
is closed and therefore the bug is closed. But their's no conspiracy
After playing around with this problem a bit it seems
running "rug sl" just once is the workaround for this bug.
Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj/
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126